jamal <hadi@xxxxxxxxxx> writes: > On Tue, 2010-02-23 at 12:00 -0800, Eric W. Biederman wrote: > >> That point of the mount to hold a persistent reference to the >> namespace without using a process. >> >> The point of the of the to be written set_ns call is to change >> the default network namespace of the process such that all future >> open/bind/socket calls happen in the referenced network namespace. > > Ok, i like it ;-> Patches RSN? Let me if you want someone to test.. My target will be 2.6.35. There is an old prototype implementation that hit the containers list and I think netdev a year or so ago. >> The are a few stray places like sysfs where it is the mount point >> not current->nsproxy->net_ns that will determine what we see. > > Is sysfs considered "usable enough" for namespaces? Mine is ;) I had a bad cold and didn't get through all of the patches this development cycle, just all the prereqs. I plan on getting that final conversation started for as soon as 2.6.34-rc1 hits. >> Attributes of the specific namespace? > > Well, example what is being un/shared etc. Got it. Implementation wise I'm going to stash a pointer to the namespace in a inode or super block, simple. Eric -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
