From owner-freebsd-current  Tue May 27 06:23:09 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id GAA12887
          for current-outgoing; Tue, 27 May 1997 06:23:09 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA12882
          for <current@FreeBSD.ORG>; Tue, 27 May 1997 06:23:06 -0700 (PDT)
Received: (from root@localhost)
	by dyson.iquest.net (8.8.5/8.8.5) id IAA00976;
	Tue, 27 May 1997 08:22:46 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199705271322.IAA00976@dyson.iquest.net>
Subject: Re: Boom! :-)
In-Reply-To: <l03020910afb05a09eb52@[194.32.164.2]> from Bob Bishop at "May 27, 97 12:56:42 pm"
To: rb@gid.co.uk (Bob Bishop)
Date: Tue, 27 May 1997 08:22:46 -0500 (EST)
Cc: karl@Mcs.Net, current@FreeBSD.ORG
Reply-To: dyson@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> Sure does. Congratulations! Looks like you've found another semi-repeatable
> way to summon up the lock gremlins! :-) :-) :-{
> 
> Seriously folks, the size of this club (people who regularly fall down
> various lock-related holes) seems to be growing. I have a little time to
> spare at the moment but I'm not up to speed with this stuff, and I have to
> say it looks unpleasant.
> 
> 
I have found one case in the VM system where the lock code is being
misused.  I'll be looking at the rest of the kernel for equiv mistakes.

John