On 03/11, Linus Torvalds 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. > > The rule about the Linux ABI is not that the ABI is set in stone. It's > that we can't break any existing binaries. And *maybe* there are users > of CLONE_PARENT and special signals, but it sounds unlikely and would > probably confuse real programs. So feel free to just try it (early in > the 3.4 merge window - not at this point, though). OK, nobody seems to object. Andrew, could you take this patch? As for self_exec_id/parent_exec_id, this needs cleanups and fixes in any case. But perhaps we can kill them after this change. 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
