From owner-cvs-all  Thu Mar 16 14:51:54 2000
Delivered-To: cvs-all@freebsd.org
Received: from holly.calldei.com (adsl-208-191-146-189.dsl.hstntx.swbell.net [208.191.146.189])
	by hub.freebsd.org (Postfix) with ESMTP
	id 51D9C37BB6E; Thu, 16 Mar 2000 14:51:51 -0800 (PST)
	(envelope-from chris@holly.calldei.com)
Received: (from chris@localhost)
	by holly.calldei.com (8.9.3/8.9.3) id QAA26799;
	Thu, 16 Mar 2000 16:51:16 -0600 (CST)
	(envelope-from chris)
Date: Thu, 16 Mar 2000 16:51:16 -0600
From: Chris Costello <chris@calldei.com>
To: Chris Costello <chris@FreeBSD.org>
Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: VOP_GETATTR/VOP_SETATTR locking expectations on 3.x?
Message-ID: <20000316165116.A24374@holly.calldei.com>
Reply-To: chris@calldei.com
References: <200003162247.OAA95515@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/0.96.4i
In-Reply-To: <200003162247.OAA95515@freefall.freebsd.org>
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thursday, March 16, 2000, Chris Costello wrote:
>   Log:
>   MFC: Make `struct vattr *' variable names consistent (vpp->vap).

   Sigh.  I just spammed the wrong revision due to confusing
numbers of xterms (fixed the file in my local RELENG_4 directory,
but committed the 4.x information into 3.x).

   Now before I go putting this back, is the following change
still inaccurate for 3.x?

-The file should not be locked on entry.
+.Xr VOP_GETATTR 9
+expects the vnode to be locked on entry and will leave the vnode locked on
+return.
+.Pp
+.Xr VOP_SETATTR 9
+expects the vnode to be locked on entry and will leave the vnode locked on
+return.

-- 
|Chris Costello <chris@calldei.com>
|Stack manipulation - the use of inflatable falsies.     -Datamazing, 4/1/78
`---------------------------------------------------------------------------


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