svn commit: r320659 - head/usr.sbin/nfsuserd

[Rick Macklem]

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?)

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).
--> 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
________________________________________
From: Olivier Cochard-Labbé <olivier at freebsd.org>
Sent: Wednesday, July 5, 2017 1:10:28 AM
To: Rick Macklem
Cc: svn-src-head; svn-src-all; src-committers; Konstantin Belousov
Subject: Re: svn commit: r320659 - head/usr.sbin/nfsuserd

On Wed, Jul 5, 2017 at 7:06 AM, Konstantin Belousov <kostikbel at gmail.com<mailto:kostikbel at gmail.com>> wrote:
On Tue, Jul 04, 2017 at 10:20:30PM +0000, Rick Macklem wrote:
> +Since the kernel communicates with the
> +.Nm
> +daemon via an upcall that uses the IP address 127.0.0.1, it does not work correctly when
> +.Xr jail 8
> +are used and can crash the system.

Does it indeed break when jails are used, or does it break when the daemon
is started in a jail ?


​And does it break on a jail/vnet too ?