CLONE_PARENT after setns(CLONE_NEWPID)
From: Serge Hallyn
Date: Wed Nov 06 2013 - 13:01:57 EST
commit 40a0d32d1eaffe6aac7324ca92604b6b3977eb0e :
"fork: unify and tighten up CLONE_NEWUSER/CLONE_NEWPID checks"
breaks lxc-attach in 3.12. That code forks a child which does
setns() and then does a clone(CLONE_PARENT). That way the
grandchild can be in the right namespaces (which the child was
not) and be a child of the original task, which is the monitor.
lxc-attach in 3.11 was working fine with no side effects that I
could see. Is there a real danger in allowing CLONE_PARENT
when current->nsproxy->pidns_for_children is not our pidns,
or was this done out of an "over-abundance of caution"? Can we
safely revert that new extra check?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/