Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 11 Mar 2012 19:37:28 +0100
From: richard -rw- weinberger <>
To: Linus Torvalds <>
Cc: Oleg Nesterov <>, Djalal Harouni <>, 
	Alan Cox <>,,, 
	Andrew Morton <>, Al Viro <>, 
	Alexey Dobriyan <>, "Eric W. Biederman" <>, 
	Vasiliy Kulikov <>, Kees Cook <>, 
	Solar Designer <>, WANG Cong <>, 
	James Morris <>,,, Greg KH <>, 
	Ingo Molnar <>, Stephen Wilson <>, "Jason A. Donenfeld" <>
Subject: Re: self_exec_id/parent_exec_id && CLONE_PARENT

On Sun, Mar 11, 2012 at 7:02 PM, Linus Torvalds
<> wrote:
> On Sun, Mar 11, 2012 at 10:49 AM, Oleg Nesterov <> 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.

Is this a problem?


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.