From owner-freebsd-fs  Fri Jan 28 14:57:41 2000
Delivered-To: freebsd-fs@freebsd.org
Received: from assaris.sics.se (dyna225-095.nada.kth.se [130.237.225.95])
	by hub.freebsd.org (Postfix) with ESMTP id 4C25D14C98
	for <fs@FreeBSD.ORG>; Fri, 28 Jan 2000 14:57:37 -0800 (PST)
	(envelope-from assar@assaris.sics.se)
Received: (from assar@localhost)
	by assaris.sics.se (8.9.3/8.9.3) id XAA82828;
	Fri, 28 Jan 2000 23:57:49 +0100 (CET)
	(envelope-from assar)
To: Robert Watson <robert+freebsd@cyrus.watson.org>
Cc: fs@FreeBSD.ORG
Subject: Re: kern/15117 seeking comitter?
References: <Pine.BSF.3.96.1000128144157.32740A-100000@fledge.watson.org>
From: Assar Westerlund <assar@sics.se>
Date: 28 Jan 2000 23:57:48 +0100
In-Reply-To: Robert Watson's message of "Fri, 28 Jan 2000 14:43:03 -0500 (EST)"
Message-ID: <5laelpdcsz.fsf@assaris.sics.se>
Lines: 15
User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Robert Watson <robert@cyrus.watson.org> writes:

Hi Robert,

> I'd be glad to commit it, but don't feel confident in my reviewing skills
> as I haven't really delved into VFS locking issues.  Is this something you
> have a chance to exhaustively test/use in a production environment?

Yes, as far as I can.  I've been running with this patch on both my
-stable and my -current machine.

And I do think it's fairly clear that the current code can lead to
dead-lock.

/assar


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message