netdev - Re: [patch net-next] vlan: Don't allow vlan devices to change network namespaces.

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:	Thu, 24 Apr 2014 07:47:34 +0200
From:	Michal Kubecek <mkubecek@...e.cz>
To:	chenweilong <chenweilong@...wei.com>
Cc:	nicolas.dichtel@...nd.com, Eric Dumazet <eric.dumazet@...il.com>,
	kaber@...sh.net, davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: [patch net-next] vlan: Don't allow vlan devices to change
 network namespaces.

On Thu, Apr 24, 2014 at 08:59:51AM +0800, chenweilong wrote:
> On 2014/4/23 15:23, Nicolas Dichtel wrote:
> > Le 23/04/2014 04:40, chenweilong a écrit :
> >> And, 2) is not safe, if someone forgets to move eth1, eth1.5 will not work, making
> >> things complex.
> > We have to fix this case, because it is a valid use case to have eth1.5 in net0
> > and eth1 in another ns.
> > 
> eth1.5 can receive and send packets in net0, the problem is you can't add a new eth1.5
> in old ns, report 'error: File exists'.

And this is correct, as far as I can tell. If it was possible, which of
the two interfaces would receive VLAN tagged packets with VID 5 coming
to eth1?

                                                         Michal Kubecek

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