[Devel] Re: [RFC][PATCH 15/16] Enable signaling child reaper from parent ns.
Dave Hansen
hansendc at us.ibm.com
Tue May 29 09:47:19 PDT 2007
On Fri, 2007-05-25 at 15:13 -0500, Serge E. Hallyn wrote:
>
> First note on that, (current == child_reaper(current)) is correct if we
> want to treat a container init as init no matter who sends the signal,
> however I contend that if a signal is sent from an ancester namespace,
> then we want to treat the task like any other task.
>
> Could I get some confirmation or rebuttal from Suka, Eric, Dave, or
> Pavel?
I agree with this. Signals should only be special when you're sending
them "up the chain" to _your_ init process. We shouldn't do anything at
all special to them when one process in a set of peers just happens to
be the init for a child namespace.
-- Dave
_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
More information about the Devel
mailing list