On Wed, May 22, 2013 at 11:35:56AM -0700, Eric W. Biederman wrote: > ebiederm@xxxxxxxxxxxx (Eric W. Biederman) writes: > > > I am missing a lot of context here and capturing the context of a > > process at time time we mount the filesystem and reconstituing it in > > call user mode helper seems like something we could do. So it's not enough just to ensure that the user namespace is set correctly? (To the namespace of the mount process in the nfs case, or of the process that starts nfsd in the nfsd case.) > If we want to do something like this the only sane thing I can see is to > have a per container version of kthread call it uthread. That the user > mode helper code would use to launch a new process. > > Anything else and I expect we will be tearing our hair out for the rest > of our lives with weird corner cases or unexpected semantics. Could you give examples of weird corner cases or unexpected semantics? --b. > At first glace I would exepct uthread to be per pid namespace in > implementation. > > Eric > > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
