netdev - Re: [PATCH net-next 1/2] vlan: don't allow vlan device to move between 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]

Message-ID: <1393592834.1744.8.camel@localhost.localdomain>
Date:	Fri, 28 Feb 2014 22:07:14 +0900
From:	Toshiaki Makita <toshiaki.makita1@...il.com>
To:	Ding Tianhong <dingtianhong@...wei.com>
Cc:	Toshiaki Makita <makita.toshiaki@....ntt.co.jp>, kaber@...sh.net,
	julia.lawall@...6.fr, joe@...ches.com, davem@...emloft.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-next 1/2] vlan: don't allow vlan device to move
 between network namespaces

On Fri, 2014-02-28 at 16:52 +0800, Ding Tianhong wrote:
> On 2014/2/28 16:12, Toshiaki Makita wrote:
> > (2014/02/28 16:50), Ding Tianhong wrote:
> >> Now the vlan device could move to another network namespace, but
> >> the read dev is sill in the old network namespace, it is unsafe
> >> and the vlan device could not work well, so don't allow to do it.
> > 
> > Why is this a problem?
> > This looks like a useful feature to me.
> > 
> > Thanks,
> > Toshiaki Makita
> > 
> I think the vlan dev is a virtual device, if it does not with real dev together,
> I am not sure whether it is correct. Maybe I miss something, pls remind me.

It can be used to aggregate/distribute traffic from/to each namespace.
We can use vlan ids as identifiers for namespaces.
If there is a problem with this usage, I don't want to disable this
feature but want to fix the exact problem.

Thanks,
Toshiaki Makita

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