Date: Wed, 03 Jun 2015 12:20:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 200585] [nlm] Fatal trap 9 when printing out KASSERT trying to run umount -f on an NFS share while it's trying to print out "lockd not responding" in nlm(4) Message-ID: <bug-200585-3630-Ju29VfsdYP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200585-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-200585-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200585 --- Comment #7 from Rick Macklem <rmacklem@FreeBSD.org> --- It's been a while since I looked at it, but I remember that there is a known issue with the client side NLM for "umount -f". Basically it unlocks and later relocks the vnode without holding a refcnt on the mount point. At the time, I didn't know enough about the mount point refcnt stuff to fix it. I'll try and take a look later to-day. I don't know if this is the cause of the crash (I can't remember what credentials are used), but it does need to be fixed for "umount -f" to be safe when running rpc.lockd. (I keep hoping people will stop using rpc.lockd and rpc.statd, but it's just a dream;-) -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200585-3630-Ju29VfsdYP>