> > No no. You don't need to do that. That's exactly what CLONE_PARENT is
> > there for. See previous example.
> 
> So would you accept CLONE_PARENT and CLONE_WAITPID patches for 2.4 ? 

Make sure CLONE_PARENT now remembers to check that the parent is part of the
same thread group - the original I believe didnt. So long as that is done
right and your thread group changes on an exec (obviously) then I think
CLONE_PARENT is safe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/