lkml.org 
[lkml]   [2012]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: self_exec_id/parent_exec_id && CLONE_PARENT
From
On Sun, Mar 11, 2012 at 7:02 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Sun, Mar 11, 2012 at 10:49 AM, Oleg Nesterov <oleg@redhat.com> wrote:
>>
>> I am also asking because the change above looks like the fix to me.
>> The child must not control its ->exit_signal, it is the parent who
>> decides which signal the child should use for notification.
>>
>> And to me, clone(CLONE_PARENT | SIGXXX) looks like a violation of
>> rule above.
>
> SIGXXX is for doing things like AIO with threads, but it would never
> be used together with CLONE_PARENT, that would be odd and wrong.
>
> So I think we could disallow that - or at least try. See if anybody
> notices, and if it breaks anything.
>

UserModeLinux is using CLONE_PARENT | CLONE_FILES | SIGCHLD.
Is this a problem?
--
Thanks,
//richard


\
 
 \ /
  Last update: 2012-03-11 19:39    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean