From: Andreas Gruenbacher <agruen@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, "Theodore T'so" <tytso@mit.edu>
Subject: Re: [PATCH] Extended attribute fixes, etc.
Date: Sat, 15 Feb 2003 18:59:11 +0100 [thread overview]
Message-ID: <200302151859.11370.agruen@suse.de> (raw)
In-Reply-To: <20030215110732.A17564@infradead.org>
On Saturday 15 February 2003 12:07, Christoph Hellwig wrote:
> On Tue, Feb 11, 2003 at 08:18:58PM +0100, Andreas Gruenbacher wrote:
> > The third to fifth are all steps towards trusted extended
> > attributes, which are useful for privileged processes (mostly
> > daemons). One use for this is Hierarchical Storage Management, in
> > which a user space daemon stores online/offline information for
> > files in trusted EA's, and the kernel communicates requests to
> > bring files online to that daemon. This class of EA's will also
> > find its way into XFS and ReiserFS, and expectedly also into JFS in
> > this form. (Trusted EAs are included in the 2.4.19/2.4.20 patches
> > as well.)
>
> Please don't do the ugly flags stuff. We have fsuids and fsgids for
> exactly that reason (and because we're still lacking a credentials
> cache..).
The XATTR_KERNEL_CONTEXT flag cannot be substituted by a uid/gid change;
it is unrelated to that; that's the whole point of it. It would be
possible to raise some other flag (such as a capability, etc.) instead
of passing an explicit flag, but that seems uglier and more
problematic/error prone to me.
-- Andreas.
next prev parent reply other threads:[~2003-02-15 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 19:18 [PATCH] Extended attribute fixes, etc Andreas Gruenbacher
2003-02-11 20:32 ` Andrew Morton
2003-02-12 11:03 ` Andreas Gruenbacher
2003-02-15 11:07 ` Christoph Hellwig
2003-02-15 17:59 ` Andreas Gruenbacher [this message]
2003-02-15 18:39 ` Christoph Hellwig
2003-02-15 19:17 ` Andreas Gruenbacher
2003-02-15 21:09 ` Christoph Hellwig
2003-02-15 21:39 ` 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=200302151859.11370.agruen@suse.de \
--to=agruen@suse.de \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.