Re: [PATCH review 1/3] pidns: Outlaw thread creation after unshare(CLONE_NEWPID)

2012-12-22 Thread Eric W. Biederman
Rob Landley writes: > On 12/21/2012 10:57:34 PM, Eric W. Biederman wrote: >> >> The sequence: >> unshare(CLONE_NEWPID) >> clone(CLONE_THREAD|CLONE_SIGHAND|CLONE_VM) >> >> Creates a new process in the new pid namespace without setting >> pid_ns->child_reaper. After forking this results in a NUL

Re: [PATCH review 1/3] pidns: Outlaw thread creation after unshare(CLONE_NEWPID)

2012-12-22 Thread Rob Landley
On 12/21/2012 10:57:34 PM, Eric W. Biederman wrote: The sequence: unshare(CLONE_NEWPID) clone(CLONE_THREAD|CLONE_SIGHAND|CLONE_VM) Creates a new process in the new pid namespace without setting pid_ns->child_reaper. After forking this results in a NULL pointer dereference. Avoid this and othe

[PATCH review 1/3] pidns: Outlaw thread creation after unshare(CLONE_NEWPID)

2012-12-21 Thread Eric W. Biederman
The sequence: unshare(CLONE_NEWPID) clone(CLONE_THREAD|CLONE_SIGHAND|CLONE_VM) Creates a new process in the new pid namespace without setting pid_ns->child_reaper. After forking this results in a NULL pointer dereference. Avoid this and other nonsense scenarios that can show up after creating a