From owner-freebsd-current@FreeBSD.ORG  Thu May  1 09:38:25 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1DB7737B401
	for <freebsd-current@freebsd.org>;
	Thu,  1 May 2003 09:38:25 -0700 (PDT)
Received: from puma.icir.org (puma.icir.org [192.150.187.73])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 943E643F3F
	for <freebsd-current@freebsd.org>;
	Thu,  1 May 2003 09:38:24 -0700 (PDT)
	(envelope-from hodson@puma.icir.org)
Received: from puma.icir.org (localhost [127.0.0.1])
	by puma.icir.org (8.12.8p1/8.12.3) with ESMTP id h41GcNUW024299;
	Thu, 1 May 2003 09:38:23 -0700 (PDT)
	(envelope-from hodson@puma.icir.org)
Message-Id: <200305011638.h41GcNUW024299@puma.icir.org>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.3
From: Orion Hodson <orion@freebsd.org>
To: Jan-Espen Pettersen <sigsegv@leakingmemory.org>
In-Reply-To: <200304302316.00929.sigsegv@leakingmemory.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 01 May 2003 09:38:23 -0700
Sender: hodson@icir.org
cc: Georg Funk <georgfunk@web.de>
cc: freebsd-current@freebsd.org
Subject: Re: lock order reversal
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2003 16:38:25 -0000


Jan-Espen

The patch looks good.  It's been parsed, tested, and committed it.  The root 
of the problem lies with chn_reset failing and hopefully there will be a fix 
for that before the 5.1 branch.

Thanks
- Orion