bridge: Export VLAN filtering state
It's useful for drivers supporting bridge offload to be able to query the bridge's VLAN filtering state. Currently, upon enslavement to a bridge master, the offloading driver will only learn about the bridge's VLAN filtering state after the bridge device was already linked with its slave. Being able to query the bridge's VLAN filtering state allows such drivers to forbid enslavement in case resource couldn't be allocated for a VLAN-aware bridge and also choose the correct initialization routine for the enslaved port, which is dependent on the bridge type. Signed-off-by: Ido Schimmel <idosch@mellanox.com> Signed-off-by: Jiri Pirko <jiri@mellanox.com> Reviewed-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:

committed by
David S. Miller

parent
5f9e27e60e
commit
1f51445af3
@@ -138,7 +138,7 @@ void br_manage_promisc(struct net_bridge *br)
|
||||
/* If vlan filtering is disabled or bridge interface is placed
|
||||
* into promiscuous mode, place all ports in promiscuous mode.
|
||||
*/
|
||||
if ((br->dev->flags & IFF_PROMISC) || !br_vlan_enabled(br))
|
||||
if ((br->dev->flags & IFF_PROMISC) || !br_vlan_enabled(br->dev))
|
||||
set_all = true;
|
||||
|
||||
list_for_each_entry(p, &br->port_list, list) {
|
||||
|
Reference in New Issue
Block a user