From: Andreas Gruenbacher <agruen@suse.de>
To: Linux-FSDevel <linux-fsdevel@vger.kernel.org>
Subject: [RFC] POSIX ACL kernel infrastructure
Date: Sun, 4 Aug 2002 15:46:35 +0200 [thread overview]
Message-ID: <200208041546.35234.agruen@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
Hello,
I want to propose adding some infrastructure to the VFS for POSIX ACL
ssupport. There are already implementations for XFS and Ext2/Ext3; ReiserFS
is to follow soon.
The design is as follows: POSIX ACLs are passed between the kernel and user
space as Extended Attributes. The patches I've mentioned are doing exactly
that. The filesystems are responsible for handling ACLs; they are not limited
to POSIX ACLs.
Filesystems may choose to cache/manipulate ACLs in the kernel internal
format that this patch implements, or differently. In any case they should
implement the get_posix_acl and set_posix_acl inode operations if mapping
between native filesystem ACLs and POSIX ACLs makes sense.
Other parts of the kernel (such as nfsd) can use the get_posix_acl and
set_posix_acl inode operations to manipulate POSIX ACLs. This is currently
required for nfsd, since nfsd must mask off permissions depending on the
protocol and client version (a module parameter controls this behavior).
(This patch also requires the ENOTSUP and MS_NOUMASK issues to be resolved.
I've posted messages on these topics to linux-kernel before, and I will send
copies to linux-fsdevel.)
Regards,
Andreas.
------------------------------------------------------------------
Andreas Gruenbacher SuSE Linux AG
mailto:agruen@suse.de Deutschherrnstr. 15-19
http://www.suse.de/ D-90429 Nuernberg, Germany
[-- Attachment #2: linux-2.5.30-posix-acl-0.diff.gz --]
[-- Type: application/x-gzip, Size: 4842 bytes --]
next reply other threads:[~2002-08-04 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 13:46 Andreas Gruenbacher [this message]
2002-08-04 14:04 ` [RFC] POSIX ACL kernel infrastructure 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
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=200208041546.35234.agruen@suse.de \
--to=agruen@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
/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