From owner-cvs-all Wed May 23 14:17:14 2001 Delivered-To: cvs-all@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id 4E8C637B424; Wed, 23 May 2001 14:17:10 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f4NLH9L04728; Wed, 23 May 2001 17:17:09 -0400 (EDT) Date: Wed, 23 May 2001 17:17:09 -0400 From: Alfred Perlstein To: John Baldwin Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_synch.c Message-ID: <20010523171709.R17514@superconductor.rush.net> References: <200105231938.f4NJcRC07053@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200105231938.f4NJcRC07053@freefall.freebsd.org>; from jhb@FreeBSD.org on Wed, May 23, 2001 at 12:38:27PM -0700 X-all-your-base: are belong to us. Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * John Baldwin [010523 15:39] wrote: > jhb 2001/05/23 12:38:27 PDT > > Modified files: > sys/kern kern_synch.c > Log: > Add in assertions to ensure that we always call msleep or mawait with > either a timeout or a held mutex to detect unprotected infinite sleeps > that can easily lead to deadlock. > > Submitted by: alfred I'm glad to see this assertion go in, however it's really not perfect, it will not detect tsleeps with a timeout without a mutex held because that is "valid". I really think we need some sort of way to really "pause" rather than wait for a signalling. Anyhow, we'll get to it one day. :) -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message