From owner-cvs-all Mon Jun 28 1:38:27 1999 Delivered-To: cvs-all@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 7DAD014CC0; Mon, 28 Jun 1999 01:38:18 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA27172; Mon, 28 Jun 1999 10:38:15 +0200 (MET DST) Date: Mon, 28 Jun 1999 10:38:13 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Kirk McKusick Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_lock.c In-Reply-To: <199906280755.AAA97764@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk Does this solve the panic discussed in current? Nick 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. > > Revision Changes Path > 1.27 +7 -5 src/sys/kern/kern_lock.c > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message