From owner-freebsd-arch  Tue Sep 26 23:13:14 2000
Delivered-To: freebsd-arch@freebsd.org
Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9])
	by hub.freebsd.org (Postfix) with ESMTP
	id 703BF37B424; Tue, 26 Sep 2000 23:13:10 -0700 (PDT)
Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA13214;
	Tue, 26 Sep 2000 23:12:38 -0700 (PDT)
Date: Tue, 26 Sep 2000 23:12:37 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Robert Watson <rwatson@FreeBSD.org>
Cc: freebsd-fs@FreeBSD.org, freebsd-arch@FreeBSD.org,
	trustedbsd-discuss@TrustedBSD.org
Subject: Re: VOP_ACCESS() and new VADMIN/VATTRIB?
In-Reply-To: <Pine.NEB.3.96L.1000926203644.79897G-100000@fledge.watson.org>
Message-ID: <Pine.BSF.4.10.10009262311160.13148-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I agree with all you have said here.


On Tue, 26 Sep 2000, Robert Watson wrote:

> 
> 
> In general, access control for operations within a file system is
> determined via a recursive VOP_ACCESS() call on the vnode, vis.
> 
> VOP_OPEN(vp, ...) -> ufs_open(vp, ...) -> VOP_ACCESS(vp, ...) ->
>     ufs_access(vp, ...)
[...]



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