[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110817141641.GA15503@redhat.com>
Date: Wed, 17 Aug 2011 16:16:41 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Kay Sievers <kay.sievers@...y.org>
Cc: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
lennart@...ttering.net, linux-man@...r.kernel.org,
roland@...k.frob.com, torvalds@...ux-foundation.org
Subject: Re: +
prctl-add-pr_setget_child_reaper-to-allow-simple-process-supervision
.patch added to -mm tree
On 08/17, Kay Sievers wrote:
>
> On Wed, Aug 17, 2011 at 15:05, Oleg Nesterov <oleg@...hat.com> wrote:
> >
> > But, I seem to remember, that patch cleared ->child_reaper on exec,
>
> I don't think he original patch did.
>
> > I think this makes sense.
>
> Why would it? Systemd can serialize its state and properly re-exec
> itself as many times as needed during its lifetime. Why would the
> kernel take something away from a process, which it explicitly asked
> for?
>
> > And I am not sure about security. No, I do not see any problems, just
> > I don't know. Say, should we check the creds during reparenting? I
> > dunno.
>
> Hmm, I don't see why that would be necessary. It's just one of our
> parents that aks for our signals.
Oh, I do not know. I do not pretend I understand the security ;)
For example. I simply can't understand why do we have security_task_wait().
Why waitpid(my_natural_child) can fail for security reasons? But we have
selinux_task_wait().
So, once again. I am not arguing. I am only asking the questions.
I didn't mean I see any problem here.
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists