[Bug 230752] panic: excl->share in newnfs_request

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Aug 19 23:25:26 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230752

Rick Macklem <rmacklem at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rmacklem at FreeBSD.org

--- Comment #1 from Rick Macklem <rmacklem at FreeBSD.org> ---
Is there a specific situation happening when these panic()s occur?
(such as startup, shutdown or ??)

Basically, the panic() happens when the kernel RPC code is doing a connect
on an AF_LOCAL socket created by the nfsuserd daemon to do an upcall.
I'll admit I haven't tested this myself recently, but I'll try running
nfsuserd on current. (prior to FreeBSD12, nfsuserd uses a UDP socket,
so this panic() wouldn't happen)
(Since unp_connectat() does a straightforward namei(), I don't know why
 there would be an "excl->shared" panic? The code is using LK_SHARED
 for the lookup, but that happens all the time.)

I am wondering if somehow the AF_LOCAL socket got deleted and that
confuses the namei()/lookup(). (The socket is /var/run/nfsuserd.sock.)

If the panic()s are causing you grief, you can add the -use-udpsock
command line option to nfsuserd to make it use the UDP socket, like FreeBSD-11.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-fs mailing list