Date: Tue, 9 Aug 2005 23:55:50 +0000 From: Alexander Kabaev <kan@freebsd.org> To: Thierry Herbelot <thierry@herbelot.com> Cc: freebsd-current@freebsd.org Subject: Re: panic: lock (sleep mutex) vnode interlock not locked Message-ID: <20050809235550.GA8692@freefall.freebsd.org> In-Reply-To: <200508092233.14912.thierry@herbelot.com> References: <200508092233.14912.thierry@herbelot.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 09, 2005 at 10:33:12PM +0200, Thierry Herbelot wrote:
> Hello,
>
> I'm seeing the above panic on two machines (SMP BP6 and a notebook) with
> recent -Current (certainly "heisenbug" : the same kernel runs happily on the
> notebook).
> The panic log on the SMP machine follows.
>
> TfH
<SKIP>
Hi,
could you try an patch below?
Index: vfs_subr.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/vfs_subr.c,v
retrieving revision 1.638
diff -u -r1.638 vfs_subr.c
--- vfs_subr.c 6 Aug 2005 01:42:03 -0000 1.638
+++ vfs_subr.c 9 Aug 2005 23:51:44 -0000
@@ -2333,10 +2333,8 @@
/*
* Don't vgonel if we're already doomed.
*/
- if (vp->v_iflag & VI_DOOMED) {
- VI_UNLOCK(vp);
+ if (vp->v_iflag & VI_DOOMED)
return;
- }
vp->v_iflag |= VI_DOOMED;
/*
* Check to see if the vnode is in use. If so, we have to call
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050809235550.GA8692>