netdev - Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

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:	Fri, 29 May 2015 07:57:31 +0200
From:	Alexander Holler <holler@...oftware.de>
To:	nicolas.dichtel@...nd.com
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	netdev@...r.kernel.org, tgraf@...g.ch, davem@...emloft.net
Subject: Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of
 netns

Am 26.05.2015 um 16:36 schrieb Alexander Holler:
> Am 26.05.2015 um 14:10 schrieb Nicolas Dichtel:
>> I don't understand why dumping in another netns is a problem.
>
> It isn't. I just wondered how you (or someone else) is using
> NETLINK_LISTEN_ALL_NSID, assuming it already serves a purpose. ;)

Maybe I should correct this, as I've lied because I got a bit bored. Sorry.

That dumping in another netns itself isn't a problem, but you need 
knowledge about the other namespaces. And if you have to go through all 
the pain to find and dump the interfaces in all other namenspaces by 
joining them, than there is not that much advantage in using 
NETLINK_LISTEN_ALL_NSID as you could still listen in another netns after 
the dump there too.

But there's no need to continue the discussion. I've understood that the 
patch series was only meant to reduce the number of sockets one 
otherwise would have continuously listen to.

Alexander Holler
--
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