From: Andreas Gruenbacher <agruen@suse.de>
To: Christoph Hellwig <hch@infradead.org>, Luka Renko <luka.renko@hermes.si>
Cc: linux-fsdevel@vger.kernel.org, torvalds@transmeta.com,
Andi Kleen <ak@suse.de>, Nathan Scott <nathans@sgi.com>,
Tim Shimmin <tes@sgi.com>, Chris Mason <mason@suse.com>,
Jeff Mahoney <jeffm@suse.com>, Dave Kleikamp <shaggy@us.ibm.com>,
Steve Best <sbest@us.ibm.com>
Subject: Re: [PATCH] backout the xattr override access checks flag
Date: Sun, 23 Feb 2003 23:16:48 +0100 [thread overview]
Message-ID: <200302232316.48664.agruen@suse.de> (raw)
In-Reply-To: <20030223193623.A21537@infradead.org>
Hello,
On Sunday 23 February 2003 20:36, Christoph Hellwig wrote:
> On Sun, Feb 23, 2003 at 08:28:23PM +0100, Luka Renko wrote:
> > I have concerns with kernel module temporarly changing capabilities of a
> > user process, however I am not sure if this is really the problem. I was
> > thinking in terms of SMP/preempt (EA calls can/will go to sleep) and
> > considering that this might be a security problem, however since we are
> > changing it per process it should probably be OK.
>
> Right. And we're already doing similar things, see sys_access().
Okay, this seems sufficient confirmation that it is not dangerous to
temporarily raise capabilities in a task, so we can get rid of the
XATTR_KERNEL_CONTEXT flag. Instead, the HSM module should raise a capability
before invoking the xattr inode operations.
-- Andreas.
next prev parent reply other threads:[~2003-02-23 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 19:28 [PATCH] backout the xattr override access checks flag Luka Renko
2003-02-23 19:36 ` Christoph Hellwig
2003-02-23 22:16 ` Andreas Gruenbacher [this message]
-- 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-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=200302232316.48664.agruen@suse.de \
--to=agruen@suse.de \
--cc=ak@suse.de \
--cc=hch@infradead.org \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luka.renko@hermes.si \
--cc=mason@suse.com \
--cc=nathans@sgi.com \
--cc=sbest@us.ibm.com \
--cc=shaggy@us.ibm.com \
--cc=tes@sgi.com \
--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.