Date: Sun, 25 Jun 2017 23:47:01 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Kernel panic in nfsv4_loadattr Message-ID: <YTXPR01MB018945E885812A551541616EDDDE0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <41f2553c-a9a6-f997-4b0a-1fe6c7603835@heuristicsystems.com.au> References: <118188c1-6507-fd83-9d6e-94e304521011@physik.tu-berlin.de> <YTXPR01MB0189AEFF9AE549885A1F1373DDDE0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>, <41f2553c-a9a6-f997-4b0a-1fe6c7603835@heuristicsystems.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Dewayne Geraghty wrote: > Rick, > A minor point. Jails don't break/disable 127.0.0.1, though it certainly > changes behaviour. > 127.0.0.1 within a jail context is reassigned the first IP that is > defined in jail.conf (or passed to the jail during creation). Ok, well I guess I should say that the change in behaviour for 127.0.0.1 ca= used by a jail breaks the nfsuserd. (The kernel code does an RPC sent over UDP t= o 127.0.0.1 to "upcall" to the nfsuserd daemon.) [good stuff about jails snipped] rick=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB018945E885812A551541616EDDDE0>