Date: Wed, 02 Dec 2015 20:05:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204949] panic: mtx_lock of spin mutex @ /usr/src/head/sys/kern/vfs_subr.c:512 Message-ID: <bug-204949-8-jaTMQazQSY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204949-8@https.bugs.freebsd.org/bugzilla/> References: <bug-204949-8@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=204949 Mateusz Guzik <mjg@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjg@FreeBSD.org --- Comment #8 from Mateusz Guzik <mjg@FreeBSD.org> --- Since the vnode change not all fields get reinitialized and chances some of "surviving" fields should not. In particular the union used to store v_mountdhere vnode is suspicious. Unfortunately I'm unable to reproduce the problem. Can you try running with the following? diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c index ddab9f0..3c39c05 100644 --- a/sys/kern/vfs_subr.c +++ b/sys/kern/vfs_subr.c @@ -2784,6 +2784,7 @@ _vdrop(struct vnode *vp, bool locked) #endif vp->v_iflag = 0; vp->v_vflag = 0; + bzero(&vp->v_un, sizeof(vp->v_un)); bo->bo_flag = 0; uma_zfree(vnode_zone, vp); } There are few more suspicious fields, but they should not matter for your issue ('clustering stuff'). -- 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-204949-8-jaTMQazQSY>