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> In-Reply-To: <200003162247.OAA95515@freefall.freebsd.org> References: <200003162247.OAA95515@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000316165116.A24374>