From: Paul Moore <paul@paul-moore.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, yangshukui <yangshukui@huawei.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kefeng Wang <wangkefeng.wang@huawei.com>,
"Guohanjun (Hanjun Guo)" <guohanjun@huawei.com>,
Qiang Huang <h.huangqiang@huawei.com>,
Lizefan <lizefan@huawei.com>, "miaoxie (A)" <miaoxie@huawei.com>,
Zhangdianfang <zhangdianfang@huawei.com>,
Eric Paris <eparis@parisplace.org>,
James Morris <james.l.morris@oracle.com>,
ebiederm@xmission.com, serge.hallyn@ubuntu.com
Subject: Re: SELinux lead to soft lockup when pid 1 proceess reap child
Date: Mon, 9 Jan 2017 18:49:36 -0500 [thread overview]
Message-ID: <CAHC9VhT+sU5bEKiHFXuopDfo=w8gULrxnpJW1zzdD7_wX-tzDw@mail.gmail.com> (raw)
In-Reply-To: <1483987383.20858.84.camel@tycho.nsa.gov>
On Mon, Jan 9, 2017 at 1:43 PM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> On Mon, 2017-01-09 at 19:29 +0100, Oleg Nesterov wrote:
>> Seriously, could someone explain why do we need the
>> security_task_wait()
>> hook at all?
>
> I would be ok with killing it.
> IIRC, the original motivation was to block an unauthorized data flow
> from child to parent when the child context differs, but part of that
> original design was also to reparent the child automatically, and that
> was never implemented. I don't think there is a real use case for it
> in practice and it just breaks things, so let's get rid of it unless
> someone objects.
Patches are always welcome, plenty of time to get things in for 4.11 :)
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2017-01-09 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58732BCF.4090908@huawei.com>
[not found] ` <58734284.1060504@huawei.com>
[not found] ` <b7f75f65-592a-5102-0ac5-4d3aa43f0b55@huawei.com>
[not found] ` <58736B2E.90201@huawei.com>
2017-01-09 18:12 ` SELinux lead to soft lockup when pid 1 proceess reap child Oleg Nesterov
2017-01-09 18:29 ` Oleg Nesterov
2017-01-09 18:43 ` Stephen Smalley
2017-01-09 23:49 ` Paul Moore [this message]
2017-01-10 0:26 ` Casey Schaufler
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='CAHC9VhT+sU5bEKiHFXuopDfo=w8gULrxnpJW1zzdD7_wX-tzDw@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=ebiederm@xmission.com \
--cc=eparis@parisplace.org \
--cc=guohanjun@huawei.com \
--cc=h.huangqiang@huawei.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=miaoxie@huawei.com \
--cc=oleg@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge.hallyn@ubuntu.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yangshukui@huawei.com \
--cc=zhangdianfang@huawei.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).