>> This patch adds a hashtable of nsproxy using the nsproxy as a key.
>> init_nsproxy is hashed at init with key 0. This is considered to be
>> the 'host' nsproxy.
> 
> hmm? how is that going to work?
> 
> I mean, a simple clone() call (on the host) will
> change the nsproxy and spawn new ones, but that
> doesn't mean that the process has left the 'host'
> it just means that some namespace is not shared
> with the 'other' processes ...

right. the new nsproxy is built with the new and old
namespaces and the id can be identify it.

nsproxy 0 is init_nsproxy which aggregates all the 
initial namespaces. 

C.
_______________________________________________
Containers mailing list
Containers@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/containers