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

[Kostik Belousov]

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070821/1eacf9f3/attachment.pgp