Re: panic excl->shared for an AF_LOCAL socket

2018-08-21 Thread Rick Macklem
Matthew Macy wrote: [stuff snipped] >I don't know what's special in this case, but I did revamp the locking there >several >months back so I'll take a look next weekend. Thanks but don't worry about it for now. I think I figured out how the panic() occurred. If the nfsd was accessing /var/run/nfs

Re: panic excl->shared for an AF_LOCAL socket

2018-08-19 Thread Matthew Macy
On Sun, Aug 19, 2018 at 4:32 PM Rick Macklem wrote: > Hi, > > PR#230752 shows a witness panic() for "excl->shared" on a vnode lock. > In this case, the kernel RPC code is trying to do a soconnect() on an > AF_LOCAL > socket. The code is unp_connectat() looks like is does a straightforward > namei

panic excl->shared for an AF_LOCAL socket

2018-08-19 Thread Rick Macklem
Hi, PR#230752 shows a witness panic() for "excl->shared" on a vnode lock. In this case, the kernel RPC code is trying to do a soconnect() on an AF_LOCAL socket. The code is unp_connectat() looks like is does a straightforward namei()/lookup(), so I am surprised to see this. Does anyone know if AF