From: Christoph Hellwig <hch@infradead.org>
To: tytso@mit.edu
Cc: 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 14:11:04 +0100 [thread overview]
Message-ID: <20021016141103.A8393@infradead.org> (raw)
In-Reply-To: <E181a3b-0006Nu-00@snap.thunk.org>; from tytso@mit.edu on Tue, Oct 15, 2002 at 06:20:55PM -0400
On Tue, Oct 15, 2002 at 06:20:55PM -0400, tytso@mit.edu wrote:
>
> The following five patches add Posix ACL support to the 2.5 kernel. The
> first three patches are generic, and will be useful to other filesystems
> who also have ACL support on deck (in particular, the JFS and XFS
> folks). The last two patches add ACL support to the ext2 and ext3
> filesystems. These patches are safe, in that the code paths remain
> largely untouched if they the compile-time option is not enabled, and
> even if ACL support is compiled in, the filesystem must be explicitly
> mounted a mount-option to enable ACL support.
>
> These pataches require that the extended attribute patches be applied
> first.
Linux, please domn't apply these ACL patches until the inode method mess is
sorted out.
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.
Or just declare the xattr representation the default one, remove
the get_posix_acl/set_posix_acl code from this code and fix up the nfsd
patch (that doesn't seem to be submitted yet) up to us the xattr
representation.
next prev parent reply other threads:[~2002-10-16 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 22:20 tytso
2002-10-16 13:11 ` Christoph Hellwig [this message]
2002-10-16 15:50 ` Theodore Ts'o
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=20021016141103.A8393@infradead.org \
--to=hch@infradead.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®