From: "Theodore Ts'o" <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>,
torvalds@transmeta.com, Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Add POSIX Access Control Lists to ext2/3
Date: Wed, 16 Oct 2002 11:50:12 -0400 [thread overview]
Message-ID: <20021016155012.GA8210@think.thunk.org> (raw)
In-Reply-To: <20021016141103.A8393@infradead.org>
On Wed, Oct 16, 2002 at 02:11:04PM +0100, Christoph Hellwig wrote:
> Ted, please either go _always_ through the {get,set}_posix_acl methods
> or never. Currently XFS doesn't know and doesn't want to know
> about the so called "egenric ACL representation" used by ext2/ext3. With
> theses methods we'd have to add it to XFS which is fine for me as long as
> it the representation generally used for working with ACLs. That would mean
> we'd have to add new syscall or at least VFS-level hooks to the xattr code.
Fine. I'll just yank the {get,set}_posix_acl methods for now. The
inode methods were only needed for the NFS code (see Andreas' comments
about the xattr interfaces being problematical for VFS support).
However, the reality is that at this point, we probably won't have
time to get support in for the NFS server ACL before feature freeze,
and changing the interface to ACL's (never mind the headaches of
trying to agree to a new syscall interface at this late date), given
the deployed userspace tools, just doesn't seem to be realistic.
So if you or Andreas has time to work on NFS server support for ACL's
in the next two days, great, but I'm going to just pass on this for
now. Later on, we can figure out what changes are necessary to all of
the various filesystems so that nfsd can get what information it
needs.
- Ted
next prev parent reply other threads:[~2002-10-16 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 22:20 [PATCH 1/5] Add POSIX Access Control Lists to ext2/3 tytso
2002-10-16 13:11 ` Christoph Hellwig
2002-10-16 15:50 ` Theodore Ts'o [this message]
2002-10-16 16:09 ` Andreas Gruenbacher
2002-10-16 22:48 ` Nathan Scott
2002-10-17 10:04 ` Andreas Gruenbacher
2002-10-17 21:55 ` Nathan Scott
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=20021016155012.GA8210@think.thunk.org \
--to=tytso@mit.edu \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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