lkml.org 
[lkml]   [2013]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectCLONE_PARENT after setns(CLONE_NEWPID)
    Hi Oleg,

    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?

    thanks,
    -serge


    \
     
     \ /
      Last update: 2013-11-06 19:41    [W:3.709 / U:0.040 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site