From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: linux-fsdevel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] backout the xattr override access checks flag
Date: Fri, 21 Feb 2003 15:54:22 +0000 [thread overview]
Message-ID: <20030221155422.A32594@infradead.org> (raw)
In-Reply-To: <200302211120.25224.agruen@suse.de>; from agruen@suse.de on Fri, Feb 21, 2003 at 11:20:25AM +0100
On Fri, Feb 21, 2003 at 11:20:25AM +0100, Andreas Gruenbacher wrote:
> > (not that such code even exists yet).
>
> There is an HSM project for which this feature has been added. I think they
> are using a loadable module.
URL?
>
> > Something even better would probably be to move out the xattr access checks
> > to common code.
>
> There are two problems with that, so this doesn't seem any better to me,
> either:
>
> (a) We would have to decode attribute names twice, once for checking
> permissions, and a second time for determining how to store them.
Doing it in the VFS would probably mean a rather large interface change
so it should be decoded only once. I.e. moving your current ext2/ext3-specific
handler abstraction to the VFS instead.
> (b) Different file systems may implement different features with different,
> file system specific limitations. The VFS layer tests would have to accept
> all potentially useful things. The file system would have to re-check.
What types of EAs do we have?
(1) user attributes - the only access checks needed are the normal DAC ones
(2) system/trusted - only privilegued access
I think that's doable.
next prev parent reply other threads:[~2003-02-21 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 3:20 [PATCH] backout the xattr override access checks flag Christoph Hellwig
2003-02-20 20:20 ` Andreas Dilger
2003-02-20 20:26 ` Christoph Hellwig
2003-02-21 10:20 ` Andreas Gruenbacher
2003-02-21 15:54 ` Christoph Hellwig [this message]
2003-02-21 16:32 ` Andreas Gruenbacher
-- strict thread matches above, loose matches on Subject: below --
2003-02-21 12:50 Luka Renko
2003-02-21 15:58 ` Christoph Hellwig
2003-02-23 19:28 Luka Renko
2003-02-23 19:36 ` Christoph Hellwig
2003-02-23 22:16 ` 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=20030221155422.A32594@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.