From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Nathan Scott <nathans@sgi.com>,
Linux-FSDevel <linux-fsdevel@vger.kernel.org>,
Olaf Kirch <okir@suse.de>, Chris Mason <mason@suse.de>,
Jeff Mahoney <jeffm@suse.com>
Subject: Re: [RFC] POSIX ACL kernel infrastructure
Date: Fri, 9 Aug 2002 13:32:46 +0100 [thread overview]
Message-ID: <20020809133246.B9622@infradead.org> (raw)
In-Reply-To: <200208091422.49879.agruen@suse.de>; from agruen@suse.de on Fri, Aug 09, 2002 at 02:22:49PM +0200
On Fri, Aug 09, 2002 at 02:22:49PM +0200, Andreas Gruenbacher wrote:
> I read this as `Why are you not returning the permissions nfsd should see in
> struct, which the inode->getattr IOP fills?'. Please correct me if this is
> not what you wanted to say.
I meant adding an acl field to struct kstat that is supposed to be filled
by ->getattr.
> The usual callers of getattr should see the unmasked permissions; it's only
> nfsd that needs this special treatment, and only on filesystems that have
> ACLs enabled. The getattr IOP is used by others as well.
So why the is a new IOP better in that respect?
> If you had adding an extra field to struct kstat in mind, this just seems too
> intrusive to me for solving the nfsd problem. The problem will go away in the
> future when all NFSv3 clients are using the ACCESS RPC, anyway. It's just a
> hack right now.
So you want to add two inode operations for a hack that is only needed to
support old NFS clients? Do you have any profiling data that shows major
overhead when going through the xattr layer?
next prev parent reply other threads:[~2002-08-09 12:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 13:46 [RFC] POSIX ACL kernel infrastructure Andreas Gruenbacher
2002-08-04 14:04 ` Christoph Hellwig
2002-08-04 14:14 ` Andreas Gruenbacher
2002-08-04 14:33 ` Christoph Hellwig
2002-08-05 12:11 ` Andreas Gruenbacher
2002-08-05 12:28 ` Christoph Hellwig
2002-08-09 2:02 ` Nathan Scott
2002-08-09 10:53 ` Andreas Gruenbacher
2002-08-09 11:15 ` Christoph Hellwig
2002-08-09 12:22 ` Andreas Gruenbacher
2002-08-09 12:32 ` Christoph Hellwig [this message]
2002-08-09 13:17 ` Andreas Gruenbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020809133246.B9622@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.de \
--cc=nathans@sgi.com \
--cc=okir@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox