From owner-cvs-all Tue Feb 5 8:58: 4 2002 Delivered-To: cvs-all@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 2887337B42B; Tue, 5 Feb 2002 08:57:58 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id g15GvuD60203; Tue, 5 Feb 2002 11:57:57 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 5 Feb 2002 11:57:56 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Brian Feldman Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/man/man9 VOP_ATTRIB.9 In-Reply-To: <200202051526.g15FQTK14036@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is this really true? While it wasn't formally true at one point, in practice I think many filesystems rely on the vnode lock to maintain the consistency of the attributes and protect them from modification. Something we should probably stick on the BSDCon summit schedule is VFS locking... Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Tue, 5 Feb 2002, Brian Feldman wrote: > green 2002/02/05 07:26:29 PST > > Modified files: > share/man/man9 VOP_ATTRIB.9 > Log: > Document that VOP_GETATTR(9) does not actually expect to hold an > exclusive lock on entry. > > Sponsored by: DARPA, NAI Labs > > Revision Changes Path > 1.14 +3 -3 src/share/man/man9/VOP_ATTRIB.9 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message