From owner-freebsd-bugs@FreeBSD.ORG  Mon Nov 19 08:29:35 2007
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 3481016A419;
	Mon, 19 Nov 2007 08:29:35 +0000 (UTC)
	(envelope-from kmacy@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 0B57A13C45B;
	Mon, 19 Nov 2007 08:29:35 +0000 (UTC)
	(envelope-from kmacy@FreeBSD.org)
Received: from freefall.freebsd.org (kmacy@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lAJ8TY2b032320;
	Mon, 19 Nov 2007 08:29:34 GMT
	(envelope-from kmacy@freefall.freebsd.org)
Received: (from kmacy@localhost)
	by freefall.freebsd.org (8.14.1/8.14.1/Submit) id lAJ8TYO9032316;
	Mon, 19 Nov 2007 08:29:34 GMT (envelope-from kmacy)
Date: Mon, 19 Nov 2007 08:29:34 GMT
Message-Id: <200711190829.lAJ8TYO9032316@freefall.freebsd.org>
To: dylan@dylex.net, kmacy@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: kmacy@FreeBSD.org
Cc: 
Subject: Re: kern/79700: [nfs] suspending nfs file access hangs other access
	to the file
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2007 08:29:35 -0000

Synopsis: [nfs] suspending nfs file access hangs other access to the file

State-Changed-From-To: open->closed
State-Changed-By: kmacy
State-Changed-When: Mon Nov 19 08:28:32 UTC 2007
State-Changed-Why: 

Suspending a process while holding a vnode lock implies that other processes
will not be able to acquire the file's vnode lock. Unfortunately, this is 
expected behaviour and not likely to change.

http://www.freebsd.org/cgi/query-pr.cgi?pr=79700