[PATCH net-next] bridge: vlan: enforce no pvid flag in vlan ranges

2015-10-11 Thread Nikolay Aleksandrov
From: Nikolay Aleksandrov Currently it's possible for someone to send a vlan range to the kernel with the pvid flag set which will result in the pvid bouncing from a vlan to vlan and isn't correct, it also introduces problems for hardware where it doesn't make sense having more than 1 pvid. iprou

Re: [PATCH net-next] bridge: vlan: enforce no pvid flag in vlan ranges

2015-10-12 Thread David Miller
From: Nikolay Aleksandrov Date: Sun, 11 Oct 2015 12:49:56 +0200 > From: Nikolay Aleksandrov > > Currently it's possible for someone to send a vlan range to the kernel > with the pvid flag set which will result in the pvid bouncing from a > vlan to vlan and isn't correct, it also introduces prob

Re: [PATCH net-next] bridge: vlan: enforce no pvid flag in vlan ranges

2015-10-11 Thread Jiri Pirko
Sun, Oct 11, 2015 at 12:49:56PM CEST, ra...@blackwall.org wrote: >From: Nikolay Aleksandrov > >Currently it's possible for someone to send a vlan range to the kernel >with the pvid flag set which will result in the pvid bouncing from a >vlan to vlan and isn't correct, it also introduces problems f