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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 May 2015 14:29:37 -0700
From:	Cong Wang <cwang@...pensource.com>
To:	Alexander Holler <holler@...oftware.de>
Cc:	Nicolas Dichtel <nicolas.dichtel@...nd.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	netdev <netdev@...r.kernel.org>, Thomas Graf <tgraf@...g.ch>,
	David Miller <davem@...emloft.net>
Subject: Re: [PATCH net-next v2 0/7] netns: ease netlink use with a lot of netns

On Fri, May 22, 2015 at 2:12 PM, Alexander Holler <holler@...oftware.de> wrote:
>>
>> Bridge doesn't have an underlying link, so no LINK_NETNSID. LINK_NETNSID
>> is only added when its underlying link is in a different netns.
>
>
> I'm using "link" similiar as interface. Maybe I've no idea what the
> attribute LINK:NETSID really means, but I've understood it as the one
> attribute which indicates the namespace an interface (or link), br0 in my
> example, lives in.
>

It is for an underlying link for example: a veth pair is a link for each other,
a tunnel device has a link to transmit packets.

Bridge and bonding are master devices where "slaves" (or ports for bridge)
can join.

netns doesn't have a name or id by nature, we assign it a name by binding
mount some /proc file, these LINK_NETNSID's are not absolutely unique either,
just relatively.
--
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