From owner-cvs-all Mon Jun 28 1:48:56 1999 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DDEF314CC0; Mon, 28 Jun 1999 01:48:50 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA29718; Mon, 28 Jun 1999 10:48:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nick Hibma Cc: Kirk McKusick , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_lock.c In-reply-to: Your message of "Mon, 28 Jun 1999 10:38:13 +0200." Date: Mon, 28 Jun 1999 10:48:08 +0200 Message-ID: <29716.930559688@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk did for me. In message , Nick Hibma writes: > >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 > > > > > > > > > > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message