On 03/11, richard -rw- weinberger wrote: > > On Sun, Mar 11, 2012 at 7:02 PM, Linus Torvalds > <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Sun, Mar 11, 2012 at 10:49 AM, Oleg Nesterov <oleg@xxxxxxxxxx> 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? This depends on how the forking process was created, and what its parent expects. If it was forked with SIGCHLD as well, then no problems. Otherwise the parent can notice the difference. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
