On Tue, Jun 14, 2022 at 02:14:35PM -0700, Kees Cook wrote: > On Sun, Jun 12, 2022 at 11:07:22PM -0700, Andrei Vagin wrote: > > Right now, a new process can't be forked in another time namespace > > if it shares mm with its parent. It is prohibited, because each time > > namespace has its own vvar page that is mapped into a process address > > space. > > > > When a process calls exec, it gets a new mm and so it could be "legal" > > to switch time namespace in that case. This was not implemented and > > now if we want to do this, we need to add another clone flag to not > > break backward compatibility. > > > > We don't have any user requests to switch times on exec except the > > vfork+exec combination, so there is no reason to add a new clone flag. > > As for vfork+exec, this should be safe to allow switching timens with > > the current clone flag. Right now, vfork (CLONE_VFORK | CLONE_VM) fails > > if a child is forked into another time namespace. With this change, > > vfork creates a new process in parent's timens, and the following exec > > does the actual switch to the target time namespace. > > This seems like a very special case. None of the other namespaces do > this, do they? > > How is CLONE_NEWTIME supposed to be used today? Time namespaces are similar to pid namespaces. If a process calls unshare(CLONE_NEWTIME) it will not change into a new time namespace. Only the children of the process will. You can also see this via /proc/<pid>/ns/time and /proc/<pid>/ns/time_for_children. After an unshare(CLONE_NEWTIME) /proc/<pid>/ns/time will be unchanged while /proc/<pid>/ns/time_for_children will reference a new time namespace. So if the process now calls fork() the child will be placed in a new time namespace. As Andrei correctly points out in the commit message each time namespace gets it's own vvar page mapped into the process address space. Consequently calls to clone*() with CLONE_VM will need to fail because it would alter the parent's mm as well. That includes vfork() which is roughly just CLONE_VM | CLONE_VFORK. fork() remains unaffected. So anything that implements a process launcher using vfork() needs to implement a fork() fallback after vfork failure() in case the original process has unshared a new time namespace. As posix spawn is implemented using vfork() we would force glibc to implement a fork() fallback and enforce the introducing of a lot of complexity to work around this. I think the proposal here makes sense and allows us to avoid introducing yet another clone flag. For vfork() it also makes sense because the calling process is suspended until exec or exit so the semantics between fork() and clone*() are sufficiently distinct to justify this difference. Iow, vfork() is distinctly targeted at enforcing an exec* call already anyway. Christian
