Date: Tue, 21 Aug 2007 00:57:40 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print]) Message-ID: <20070821045739.GA83774@rot26.obsecurity.org> In-Reply-To: <20070820205201.GW2738@deviant.kiev.zoral.com.ua> References: <200708202340.29678.qpadla@gmail.com> <20070820205201.GW2738@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 20, 2007 at 11:52:01PM +0300, Kostik Belousov wrote: > Quite often, the "impossible" panics with vnode locking are happens > because some other thread already paniced the kernel. Then, lockmgr > passes all lock requests without actually locking. I would suggest > looking around to make sure this is not the case there. Is there a good reason to be doing that? Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070821045739.GA83774>