LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: serge@hallyn.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelyanov <xemul@openvz.org>,
Oleg Nesterov <oleg@tv-sign.ru>,
linux-kernel@vger.kernel.org, Andrew Morgan <morgan@kernel.org>
Subject: Re: Fw: [PATCH 1/1] file capabilities: simplify signal check
Date: Thu, 28 Feb 2008 13:25:01 -0700 [thread overview]
Message-ID: <m1tzjs4yn6.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20080227043306.GA9293@vino.hallyn.com> (serge@hallyn.com's message of "Tue, 26 Feb 2008 22:33:06 -0600")
serge@hallyn.com writes:
> Quoting Eric W. Biederman (ebiederm@xmission.com):
>> Andrew Morton <akpm@linux-foundation.org> writes:
>>
>> > um, is that code namespace-clean?
>>
>> Choke, gag.
>
> Oh, sorry, I got lost in the set of patches in the message. To be
> clear, my little 4-patch uid-ns-signal patchset can simply be updated
> to make the cap_task_kill() uid check into if (task_user_equiv(current, p)
>
> But Eric if you simply drop cap_task_kill() (don't make it return 0,
> just drop the function and go back to not setting task_kill in the
> capability_security_ops) I'll ack that. Else I'll write the patch
> thursday. At this point the only thing that will be denied by
> cap_task_kill() but not by check_kill_permission() is funky euid cases.
> That's wrong. (cc'ing amorgan in the event I'm forgetting something
> useful the fn is doing)
Go ahead. I'm fighting a cold and am fairly overloaded at the moment.
Eric
next prev parent reply other threads:[~2008-02-28 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080223000237.518aace0.akpm@linux-foundation.org>
2008-02-24 6:50 ` Eric W. Biederman
2008-02-24 18:09 ` Oleg Nesterov
2008-02-24 21:08 ` Harald Welte
2008-02-25 18:23 ` Oleg Nesterov
2008-02-27 4:18 ` serge
2008-02-27 4:33 ` serge
2008-02-28 20:25 ` Eric W. Biederman [this message]
2008-02-28 21:35 ` serge
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=m1tzjs4yn6.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=oleg@tv-sign.ru \
--cc=serge@hallyn.com \
--cc=xemul@openvz.org \
--subject='Re: Fw: [PATCH 1/1] file capabilities: simplify signal check' \
/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
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).