[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <wihvab6eded.fsf@dev-r-vrt-156.mtr.labs.mlnx>
Date: Tue, 29 May 2018 17:37:30 +0300
From: Petr Machata <petrm@...lanox.com>
To: Ilias Apalodimas <ilias.apalodimas@...aro.org>
Cc: netdev@...r.kernel.org, devel@...verdev.osuosl.org,
bridge@...ts.linux-foundation.org, jiri@...lanox.com,
idosch@...lanox.com, davem@...emloft.net,
razvan.stefanescu@....com, gregkh@...uxfoundation.org,
stephen@...workplumber.org, andrew@...n.ch,
vivien.didelot@...oirfairelinux.com, f.fainelli@...il.com,
nikolay@...ulusnetworks.com
Subject: Re: [PATCH net-next v2 3/7] rocker: rocker_main: Ignore bridge VLAN events
Ilias Apalodimas <ilias.apalodimas@...aro.org> writes:
>> diff --git a/drivers/net/ethernet/rocker/rocker_main.c b/drivers/net/ethernet/rocker/rocker_main.c
>> index e73e4fe..aeafdb9 100644
>> --- a/drivers/net/ethernet/rocker/rocker_main.c
>> +++ b/drivers/net/ethernet/rocker/rocker_main.c
>> @@ -1632,6 +1632,9 @@ rocker_world_port_obj_vlan_add(struct rocker_port *rocker_port,
>> {
>> struct rocker_world_ops *wops = rocker_port->rocker->wops;
>>
>> + if (netif_is_bridge_master(vlan->obj.orig_dev))
>> + return -EOPNOTSUPP;
>> +
> What will happen to the "bridge vlan add dev br0 vid X pvid untagged self" when
> the lower level (the driver) returns -EOPNOTSUPP? Will it avoid adding a vlan on
> the bridge ?
No, it will still do it. The reasons are:
- that's what currently happens anyway: none of the drivers has any
support, yet the bridge logic is done
- -EOPNOTSUPP is what switchdev_port_obj_*() return if switchdev is not
compiled in
In order to suppress the setting, return e.g. -EINVAL:
# bridge vlan add dev br vid 111 self
RTNETLINK answers: Invalid argument
# bridge vlan show dev br
port vlan ids
br 1 PVID Egress Untagged
Thanks,
Petr
Powered by blists - more mailing lists