lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 30 Oct 2008 15:41:17 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Vivien Chappelier <vivien.chappelier@...mson.net>,
	netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Benjamin Thery <benjamin.thery@...l.net>, jleu@...dspring.com,
	linux-vrf-general@...ts.sourceforge.net
Subject: Re: [PATCH 6/6] netns: configurable number of initial network	namespaces

Patrick McHardy <kaber@...sh.net> writes:

> Vivien Chappelier wrote:
>>    Yes; the linux-vrf patches had a new netlink message to create/remove the
>> equivalent of a network namespace (ip vrf add 1). I've not ported this feature
>> yet, so this patch is meant to provide another way of setting up networking
>> stacks without the need for a new process for each stack. The ability to
>> dynamically create/remove networking stacks from userspace would definitely be
>> useful.
>
> I see, I didn't realize the process that created a namespace
> needs to be kept running. So yes, creating standalone network
> namespaces seems to make sense

To be clear a reference needs to be kept to the network namespace.
Either by being the network namespace that new sockets are created in
task->nsproxy->netns or the network namespace of an open socket sock_net(sk).

If neither of those two conditions hold the network namespace count drops to
zero and it will be freed.  Probably not ideal if you are just doing routing.

Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ