Date: Tue, 21 Aug 2007 14:35:04 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Kris Kennaway <kris@obsecurity.org> 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: <20070821113504.GA2738@deviant.kiev.zoral.com.ua> In-Reply-To: <20070821045739.GA83774@rot26.obsecurity.org> References: <200708202340.29678.qpadla@gmail.com> <20070820205201.GW2738@deviant.kiev.zoral.com.ua> <20070821045739.GA83774@rot26.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--ZkFfH+RuFRkNoGBj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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: >=20 > > 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. >=20 > 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. --ZkFfH+RuFRkNoGBj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGys3oC3+MBN1Mb4gRArAqAJ9w/FQO+olZbKzDCAXJqcksJWglpgCcCyHd GpmncZJbSn6bNciIUBrK5LU= =oExS -----END PGP SIGNATURE----- --ZkFfH+RuFRkNoGBj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070821113504.GA2738>