From: Christoph Hellwig <hch@infradead.org>
To: Luka Renko <luka.renko@hermes.si>
Cc: Andreas Gruenbacher <agruen@suse.de>,
Christoph Hellwig <hch@sgi.com>,
linux-fsdevel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] backout the xattr override access checks flag
Date: Fri, 21 Feb 2003 15:58:34 +0000 [thread overview]
Message-ID: <20030221155834.B32594@infradead.org> (raw)
In-Reply-To: <A1C30C1C0FB8D5118D810004754C0375966728@hsl-lj3x.hermes.si>; from luka.renko@hermes.si on Fri, Feb 21, 2003 at 01:50:33PM +0100
On Fri, Feb 21, 2003 at 01:50:33PM +0100, Luka Renko wrote:
> I would agree with Andreas that temporarily raising capabilities for process
> by kernel module is probably not a good thing. I think having the flag (that
> cannot be passed from user space) is better.
So could you please explain why this is better in your eyes?
> Any HSM kernel module is potential user of this. The project I am working is
> currently doing capability/permission modifications to allow writing EAs in
> some cases.
SGI's dmapi implementation doesn't need it.. (it uses the proper credentials
passing in XFS instead, something we should have at the VFS level but
unfortunately 2.5 once again didn't get this)
next prev parent reply other threads:[~2003-02-21 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 12:50 [PATCH] backout the xattr override access checks flag Luka Renko
2003-02-21 15:58 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-23 19:28 Luka Renko
2003-02-23 19:36 ` Christoph Hellwig
2003-02-23 22:16 ` Andreas Gruenbacher
2003-02-21 3:20 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
2003-02-21 16:32 ` 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=20030221155834.B32594@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=hch@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luka.renko@hermes.si \
--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;
as well as URLs for NNTP newsgroup(s).