Messages in this thread | | | Date | Wed, 25 Feb 2009 12:06:53 -0800 (PST) | From | Linus Torvalds <> | Subject | Re: [PATCH 1/2] copy_process: fix CLONE_PARENT && ->exit_signal interaction |
| |
On Wed, 25 Feb 2009, Roland McGrath wrote: > > As I think I said before, I don't really know what the actual use case is > for CLONE_PARENT without CLONE_THREAD. So it's easy to approve changing > its behavior, but I do vaguely worry about who expected what behavior before.
I think changing it is wrong.
I can easily see somebody using CLONE_PARENT to get the correct getppid semantics in the thread, and then setting the signal to zero to not make the parent see the thread go away. I think both yours and Oleg's patch break that.
And there _are_ programs that have used clone() directly - not using any pthreads emulation layer. Some game used it for audio threads etc.
So at the very least it should accept zero for "no signal". And quite frankly, it would be good to try to see if there are other alternatives.
Linus
| |