From: Ido Schimmel <idosch@mellanox.com>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: Nikolay Aleksandrov <razor@blackwall.org>,
<netdev@vger.kernel.org>, <sfeldma@gmail.com>, <jiri@resnulli.us>,
<davem@davemloft.net>,
"Nikolay Aleksandrov" <nikolay@cumulusnetworks.com>,
<eladr@mellanox.com>
Subject: Re: [PATCH net-next] switchdev: enforce no pvid flag in vlan ranges
Date: Tue, 13 Oct 2015 11:31:52 +0300 [thread overview]
Message-ID: <20151013083111.GA1432@colbert.mtl.com> (raw)
In-Reply-To: <20151012173625.GA17983@ketchup.lan>
Mon, Oct 12, 2015 at 08:36:25PM IDT, vivien.didelot@savoirfairelinux.com wrote:
>Hi guys,
>
>On Oct. Monday 12 (42) 02:01 PM, Nikolay Aleksandrov wrote:
>> From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>>
>> We shouldn't allow BRIDGE_VLAN_INFO_PVID flag in VLAN ranges.
>>
>> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>> ---
>> net/switchdev/switchdev.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/net/switchdev/switchdev.c b/net/switchdev/switchdev.c
>> index 6e4a4f9ad927..256c596de896 100644
>> --- a/net/switchdev/switchdev.c
>> +++ b/net/switchdev/switchdev.c
>> @@ -720,6 +720,9 @@ static int switchdev_port_br_afspec(struct net_device *dev,
>> if (vlan.vid_begin)
>> return -EINVAL;
>> vlan.vid_begin = vinfo->vid;
>> + /* don't allow range of pvids */
>> + if (vlan.flags & BRIDGE_VLAN_INFO_PVID)
>> + return -EINVAL;
>> } else if (vinfo->flags & BRIDGE_VLAN_INFO_RANGE_END) {
>> if (!vlan.vid_begin)
>> return -EINVAL;
>> --
>> 2.4.3
>>
>
>Yes the patch looks good, but it is a minor check though. I hope the
>subject of this thread is making sense.
>
>VLAN ranges seem to have been included for an UX purpose (so commands
>look like Cisco IOS). We don't want to change any existing interface, so
>we pushed that down to drivers, with the only valid reason that, maybe
>one day, an hardware can be capable of programming a range on a per-port
>basis.
Hi,
That's actually what we are doing in mlxsw. We can do up to 256 entries in
one go. We've yet to submit this part.
>
>So what happens is that we'll add some code to fix and check non-sense
>(e.g. range + PVID) in switchdev, bridge, and I'm sure we are missing
>other spots.
>
>Sorry for being insistent, but this still doesn't look right to me.
>
>It seems like we are bloating bridge, switchdev and drivers for the only
>reason to maintain a kernel support for something like:
>
> # for i in $(seq 100 4000); do bridge vlan add vid $i dev swp0; done
>
>Thanks,
>-v
>--
>To unsubscribe from this list: send the line "unsubscribe netdev" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-13 8:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 23:30 switchdev and VLAN ranges Vivien Didelot
2015-10-10 4:22 ` Scott Feldman
2015-10-10 16:33 ` Vivien Didelot
2015-10-10 18:10 ` Florian Fainelli
2015-10-10 19:47 ` Vivien Didelot
2015-10-10 7:49 ` Elad Raz
2015-10-10 10:36 ` Nikolay Aleksandrov
2015-10-11 7:12 ` Jiri Pirko
2015-10-11 10:49 ` [PATCH net-next] bridge: vlan: enforce no pvid flag in vlan ranges Nikolay Aleksandrov
2015-10-11 14:13 ` Jiri Pirko
2015-10-13 2:59 ` David Miller
2015-10-11 22:41 ` switchdev and VLAN ranges Vivien Didelot
2015-10-12 0:13 ` Nikolay Aleksandrov
2015-10-12 5:14 ` Scott Feldman
2015-10-12 10:15 ` Nikolay Aleksandrov
2015-10-12 12:01 ` [PATCH net-next] switchdev: enforce no pvid flag in vlan ranges Nikolay Aleksandrov
2015-10-12 12:11 ` Elad Raz
2015-10-12 12:17 ` Jiri Pirko
2015-10-12 17:36 ` Vivien Didelot
2015-10-13 6:13 ` Scott Feldman
2015-10-13 8:31 ` Ido Schimmel [this message]
2015-10-13 14:32 ` Vivien Didelot
2015-10-14 6:14 ` Ido Schimmel
2015-10-14 15:25 ` Vivien Didelot
2015-10-14 17:14 ` Scott Feldman
2015-10-14 17:42 ` Ido Schimmel
2015-10-14 18:51 ` Vivien Didelot
2015-10-14 22:08 ` Florian Fainelli
2015-10-15 0:07 ` Vivien Didelot
2015-10-15 2:58 ` Scott Feldman
2015-10-15 7:28 ` Ido Schimmel
2015-10-13 11:42 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151013083111.GA1432@colbert.mtl.com \
--to=idosch@mellanox.com \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=razor@blackwall.org \
--cc=sfeldma@gmail.com \
--cc=vivien.didelot@savoirfairelinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).