On Tue, Apr 19, 2005 at 05:13:32PM -0500, Eric Van Hensbergen wrote: > The motivation behind this patch is to make private namespaces more > accessible by allowing their creation at mount/bind time. > > Based on some of the FUSE permissions discussions, I wanted to check > into modifying the mount system calls -- adding a flag which created a > new namespace for the resulting mount. I quickly discovered that what > I typically wanted (for the case of running a mount command) was to > actually create a new namespace for the parent thread (typically the > shell), inherit that namespace, and then perform the mount. > > Its not clear to me that both options are needed, cloning the parent's > namespace seems to be what you want most of the time. > > In order to minimize code impact I split the copy_namespace function, > perhaps the right long term solution is to change it's interface to > accommodate the changes. Things look a bit more invasive as I moved > the copy_namespace function above do_mount. The patch follows:
*UGH* So what happens to those who happen to share task->fs with the parent? - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
