Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 5 Jul 2017 18:43:47 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        Olivier Cochard-Labb?? <olivier@freebsd.org>, Rick Macklem <rmacklem@FreeBSD.org>, svn-src-head <svn-src-head@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, src-committers <src-committers@freebsd.org>
Subject:   Re: svn commit: r320659 - head/usr.sbin/nfsuserd
Message-ID:  <20170705154346.GW1935@kib.kiev.ua>
In-Reply-To: <YTXPR01MB018984047AB4E0A3C1247024DDD40@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
References:  <201707042220.v64MKU77039219@repo.freebsd.org> <20170705050637.GT1935@kib.kiev.ua> <CA%2Bq%2BTcpiqPzjGje0C%2BQ2WrOqAG2c6LrziirgjiCiN2OTkgDY3A@mail.gmail.com> <YTXPR01MB018984047AB4E0A3C1247024DDD40@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 05, 2017 at 11:58:56AM +0000, Rick Macklem wrote:
> Well, I know nothing about jails, so I can't answer either of these.
> All I can tell you is that 127.0.0.1 no longer works as localhost when
> jails are run for some situations which I don't understand and that
> breaks the nfsuserd upcall. (Something about 127.0.0.1 being replaced
> by the first IP# for the net interface when jails are running?)
When a jailed process uses a local address, the address is effectively
replaced by the jailed address, as you noted above.

> 
> The patches in PR#205193 change nfsuserd to use a local socket,
> which fixes this problem. However, the original poster of the PR had
> hangs when using the patches which was never resolved (I couldn't
> reproduce the hang).
So consider the issue not reproducable and test it in wild by committing
to HEAD.  Ability to do such kind of experiment is one of the reasons why
do we have HEAD and separate release branches.


> --> It has been a couple of years, but I recall that the hang was in the
>       unix socket code, so I believed it was caused by having mutiple
>       processes trying to use the socket concurrently.
>       --> The original poster never confirmed if using a single daemon
>             avoided the hang.
> As such I am stuck until someone can test the patches? rick



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170705154346.GW1935>