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] [thread-next>] [day] [month] [year] [list]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F919440808@HASMSX110.ger.corp.intel.com>
Date:	Thu, 17 Sep 2015 09:51:21 +0000
From:	"Rosen, Rami" <rami.rosen@...el.com>
To:	Rick Jones <rick.jones2@...com>, Ani Sinha <ani@...sta.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: list of all network namespaces

Hi,

>Presumably you could copy what "ip netns" does, which appears to be to look in /var/run/netns .  At least that is what an strace of that >command suggests.

This is true, but keep in mind that the output of "ip netns", as well as listing the contents of /var/run/netns, reflects only network namespaces
which were created with the "ip netns" command. The "ip netns" userspace implementation consists of code which enables this,
by creating /var/run/netns, bind mounting it, etc.

Network namespaces which were created by other ways (like userspace applications
using the clone() system call) will *not* be reflected by neither of them.

Regards,
Rami Rosen
Intel Corporation


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ