From owner-freebsd-hackers@FreeBSD.ORG  Thu Aug  7 11:21:22 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 85A7337B401
	for <freebsd-hackers@freebsd.org>;
	Thu,  7 Aug 2003 11:21:22 -0700 (PDT)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3B0FD43F85
	for <freebsd-hackers@freebsd.org>;
	Thu,  7 Aug 2003 11:21:21 -0700 (PDT)	(envelope-from silby@silby.com)
Received: (qmail 43755 invoked from network); 7 Aug 2003 18:21:19 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 7 Aug 2003 18:21:19 -0000
X-pair-Authenticated: 209.68.2.70
Date: Thu, 7 Aug 2003 13:18:50 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Robert Watson <rwatson@freebsd.org>
In-Reply-To: <Pine.NEB.3.96L.1030807141440.20722A-100000@fledge.watson.org>
Message-ID: <20030807131751.G38264@odysseus.silby.com>
References: <Pine.NEB.3.96L.1030807141440.20722A-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-hackers@freebsd.org
Subject: Re: possible deadlocks?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Aug 2003 18:21:23 -0000


On Thu, 7 Aug 2003, Robert Watson wrote:

> On Wed, 6 Aug 2003, Ted Unangst wrote:
>
> > My advisor Dawson Engler has written a deadlock detector, and we'd like
> > some verification. They look like bugs, unless there is some other
> > reason why two call chains cannot happen at the same time.
>
> Neat -- sounds like two good catches given the responses so far.  Can we
> expect more such reports forthcoming?  This kind of help will be
> invaluable in finishing up the fine-grained locking work.  Alternatively,
> do you plan to post the software?  Is this static or dynamic analysis?
> etc, etc?  :-)
>
> Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
> robert@fledge.watson.org      Network Associates Laboratories

Just for everyone's info, any locking problems that I introduce over the
next few months will not be mistakes, they will be "test cases" for the
deadlock detector.

Mike "Silby" Silbersack