Re: And probably the final crash for today's current :) (panic: filesystem goof: vop_panic[vop_print])

From: Kostik Belousov <kostikbel_at_gmail.com>
Date: Tue, 21 Aug 2007 14:35:04 +0300
On Tue, Aug 21, 2007 at 12:57:40AM -0400, Kris Kennaway wrote:
> 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?

Hmm. This is revision 1.47 of sys/kern/kern_lock.c:
date: 2001/08/10 23:29:15;  author: jhb;  state: Exp;  lines: +6 -1
If we've panic'd already, then just bail in lockmgr rather than blocking or
possibly panic'ing again.

Received on Tue Aug 21 2007 - 09:35:12 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:16 UTC