Date: Tue, 29 Jun 1999 08:54:25 +0930 From: Greg Lehey <grog@lemis.com> To: Nick Hibma <nick.hibma@jrc.it> Cc: Kirk McKusick <mckusick@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_lock.c Message-ID: <19990629085424.X43194@freebie.lemis.com> In-Reply-To: <Pine.GSO.3.95q.990628103756.4320U-100000@elect8>; from Nick Hibma on Mon, Jun 28, 1999 at 10:38:13AM %2B0200 References: <199906280755.AAA97764@freefall.freebsd.org> <Pine.GSO.3.95q.990628103756.4320U-100000@elect8>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 28 June 1999 at 10:38:13 +0200, Nick Hibma wrote: > On Mon, 28 Jun 1999, Kirk McKusick wrote: > >> mckusick 1999/06/28 00:55:01 PDT >> >> Modified files: >> sys/kern kern_lock.c >> Log: >> When requesting an exclusive lock with LK_NOWAIT, do not panic >> if LK_RECURSIVE is not set, as we will simply return that the >> lock is busy and not actually deadlock. This allows processes >> to use polling locks against buffers that they may already >> hold exclusively locked. > > Does this solve the panic discussed in current? Which one? It didn't solve the panic out of breadn(): dd if=/dev/da1b of=/dev/null bs=120b Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990629085424.X43194>