lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 28 Jun 2007 17:12:01 +0400
From:	Kirill Korotaev <>
To:	Ben Greear <>
CC:	Patrick McHardy <>,
	"Eric W. Biederman" <>,
	Jeff Garzik <>,
	YOSHIFUJI Hideaki <>,, jamal <>,
	Linux Containers <>,
	Stephen Hemminger <>,
	David Miller <>
Subject: Re: [Devel] Re: [RFD] L2 Network namespace infrastructure

Ben Greear wrote:
> Kirill Korotaev wrote:
>>Patrick McHardy wrote:
>>>I believe OpenVZ stores the current namespace somewhere global,
>>>which avoids passing the namespace around. Couldn't you do this
>>>as well?
>>yes, we store a global namespace context on current
>>(can be stored in per-cpu as well).
>>do you prefer this way?
> For what it's worth, I don't prefer this way as I can see wanting to 
> have one application
> use several namespaces at once....

As I wrote to you in another email, it's not a problem,
since applications itself do not own network namespace.

It is objects like sockets which are binded to net namespace and thus
you can have sockets from different namespaces in one application
regardless of mechanism of context handling we talk about.


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists