RX filtering in DSA
Subsystems (4)
Vladimir Oltean
maintainerv3 cover RX filtering in DSA
From: Vladimir Oltean <[email protected]>
Patch series is sent as RFC due to its dependency on the "Cleanup for the bridge replay helpers" which has not yet been applied:
https://patchwork.kernel.org/project/netdevbpf/cover/[email protected]/
Sending just for early review, I'm hoping that there is still enough time for a proper submission before the development cycle closes.
This is my third stab at creating a list of unicast and multicast addresses that the DSA CPU ports must trap. I am reusing a lot of Tobias's work which he submitted here:
https://patchwork.kernel.org/project/netdevbpf/cover/[email protected]/
My additions to Tobias' work come in the form of taking some care that additions and removals of host addresses are properly balanced, so that we can do reference counting on them for cross-chip setups and multiple bridges spanning the same switch (I am working on an NXP board where both are real requirements).
During the last attempted submission of multiple CPU ports for DSA:
https://patchwork.kernel.org/project/netdevbpf/cover/[email protected]/
it became clear that the concept of multiple CPU ports would not be compatible with the idea of address learning on those CPU ports (when those CPU ports are statically assigned to user ports, not in a LAG) unless the switch supports complete FDB isolation, which most switches do not. So DSA needs to manage in software all addresses that are installed on the CPU port(s), which is what this patch set does.
Compared to all earlier attempts, this series does not fiddle with how DSA operates the ports in standalone mode at all, just when bridged. We need to sort that out properly, then any optimization that comes in standalone mode (i.e. IFF_UNICAST_FLT) can come later.
Tobias Waldekranz (3):
net: bridge: switchdev: send FDB notifications for host addresses
net: dsa: sync static FDB entries on foreign interfaces to hardware
net: dsa: include bridge addresses which are local in the host fdb
list
Vladimir Oltean (12):
net: bridge: allow br_fdb_replay to be called for the bridge device
net: bridge: allow br_mdb_replay to be called for the bridge device
net: dsa: delete dsa_legacy_fdb_add and dsa_legacy_fdb_del
net: dsa: introduce dsa_is_upstream_port and dsa_switch_is_upstream_of
net: dsa: introduce a separate cross-chip notifier type for host MDBs
net: dsa: reference count the MDB entries at the cross-chip notifier
level
net: dsa: introduce a separate cross-chip notifier type for host FDBs
net: dsa: reference count the FDB addresses at the cross-chip notifier
level
net: dsa: install the host MDB and FDB entries in the master's RX
filter
net: dsa: include fdb entries pointing to bridge in the host fdb list
net: dsa: ensure during dsa_fdb_offload_notify that dev_hold and
dev_put are on the same dev
net: dsa: replay the local bridge FDB entries pointing to the bridge
dev too
include/net/dsa.h | 39 ++++++ net/bridge/br_fdb.c | 7 +- net/bridge/br_mdb.c | 3 +- net/bridge/br_private.h | 7 +- net/bridge/br_switchdev.c | 11 +- net/dsa/dsa2.c | 14 ++ net/dsa/dsa_priv.h | 14 ++ net/dsa/port.c | 86 ++++++++++++ net/dsa/slave.c | 102 +++++++------- net/dsa/switch.c | 276 +++++++++++++++++++++++++++++++++++++- 10 files changed, 490 insertions(+), 69 deletions(-)
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 1/15 net: bridge: switchdev: send FDB notifications for host addresses
From: Tobias Waldekranz <[email protected]>
Treat addresses added to the bridge itself in the same way as regular ports and send out a notification so that drivers may sync it down to the hardware FDB.
--- net/bridge/br_fdb.c | 4 ++-- net/bridge/br_private.h | 7 ++++--- net/bridge/br_switchdev.c | 11 +++++------ 3 files changed, 11 insertions(+), 11 deletions(-)
net/bridge/br_fdb.c +2 -2
@@ -602,7 +602,7 @@ void br_fdb_update(struct net_bridge *br, struct net_bridge_port *source,/* fastpath: update of existing entry */ if (unlikely (source != fdb->dst && !test_bit (BR_FDB_STICKY , &fdb->flags))) { -br_switchdev_fdb_notify (fdb,RTM_DELNEIGH ); +br_switchdev_fdb_notify (br, fdb,RTM_DELNEIGH ); fdb->dst = source; fdb_modified = true;/* Take over HW learned entry */
@@ -794,7 +794,7 @@ static void fdb_notify(struct net_bridge *br,int err = -ENOBUFS ;if (swdev_notify) -br_switchdev_fdb_notify (fdb, type); +br_switchdev_fdb_notify (br, fdb, type); skb =nlmsg_new (fdb_nlmsg_size (),GFP_ATOMIC );if (skb ==NULL )
net/bridge/br_private.h +4 -3
@@ -1654,8 +1654,8 @@ int br_switchdev_set_port_flag(struct net_bridge_port *p,unsigned long flags, unsigned long mask, struct netlink_ext_ack *extack); -void br_switchdev_fdb_notify (const struct net_bridge_fdb_entry *fdb, -int type); +void br_switchdev_fdb_notify (struct net_bridge *br, +const struct net_bridge_fdb_entry *fdb,int type);int br_switchdev_port_vlan_add (struct net_device *dev,u16 vid,u16 flags,struct netlink_ext_ack *extack);int br_switchdev_port_vlan_del (struct net_device *dev,u16 vid);
@@ -1702,7 +1702,8 @@ static inline int br_switchdev_port_vlan_del(struct net_device *dev, u16 vid) }static inline void -br_switchdev_fdb_notify (const struct net_bridge_fdb_entry *fdb,int type) +br_switchdev_fdb_notify (struct net_bridge *br, +const struct net_bridge_fdb_entry *fdb,int type) { }
net/bridge/br_switchdev.c +5 -6
@@ -108,7 +108,8 @@ int br_switchdev_set_port_flag(struct net_bridge_port *p, }void -br_switchdev_fdb_notify (const struct net_bridge_fdb_entry *fdb,int type) +br_switchdev_fdb_notify (struct net_bridge *br, +const struct net_bridge_fdb_entry *fdb,int type) {struct switchdev_notifier_fdb_info info = { .addr = fdb->key.addr.addr,
@@ -117,18 +118,16 @@ br_switchdev_fdb_notify(const struct net_bridge_fdb_entry *fdb, int type) .is_local = test_bit(BR_FDB_LOCAL, &fdb->flags), .offloaded = test_bit(BR_FDB_OFFLOADED, &fdb->flags), }; - -if (!fdb->dst) -return ; +struct net_device *dev = fdb->dst ? fdb->dst->dev : br->dev;switch (type) {case RTM_DELNEIGH :call_switchdev_notifiers (SWITCHDEV_FDB_DEL_TO_DEVICE , - fdb->dst->dev, &info.info,NULL ); + dev, &info.info,NULL );break ;case RTM_NEWNEIGH :call_switchdev_notifiers (SWITCHDEV_FDB_ADD_TO_DEVICE , - fdb->dst->dev, &info.info,NULL ); + dev, &info.info,NULL );break ; } }
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 2/15 net: bridge: allow br_fdb_replay to be called for the bridge device
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
When a port joins a bridge which already has local FDB entries pointing to the bridge device itself, we would like to offload those, so allow the "dev" argument to be equal to the bridge too. The code already does what we need in that case.
--- net/bridge/br_fdb.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/bridge/br_fdb.c +2 -1
@@ -754,7 +754,8 @@ int br_fdb_replay(const struct net_device *br_dev, const struct net_device *dev,unsigned long action;int err =0 ; -if (!netif_is_bridge_master (br_dev) || !netif_is_bridge_port (dev)) +if (!netif_is_bridge_master (br_dev) || + (!netif_is_bridge_port (dev) && !netif_is_bridge_master (dev)))return -EINVAL ; br =netdev_priv (br_dev);
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 3/15 net: bridge: allow br_mdb_replay to be called for the bridge device
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
--- net/bridge/br_mdb.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/bridge/br_mdb.c +2 -1
@@ -617,7 +617,8 @@ int br_mdb_replay(struct net_device *br_dev, struct net_device *dev,ASSERT_RTNL (); -if (!netif_is_bridge_master (br_dev) || !netif_is_bridge_port (dev)) +if (!netif_is_bridge_master (br_dev) || + (!netif_is_bridge_port (dev) && !netif_is_bridge_master (dev)))return -EINVAL ; br =netdev_priv (br_dev);
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 4/15 net: dsa: delete dsa_legacy_fdb_add and dsa_legacy_fdb_del
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
We want to add reference counting for FDB entries in cross-chip topologies, and in order for that to have any chance of working and not be unbalanced (leading to entries which are never deleted), we need to ensure that higher layers are sane, because if they aren't, it's garbage in, garbage out.
For example, if we add a bridge FDB entry twice, the bridge properly errors out:
$ bridge fdb add dev swp0 00:01:02:03:04:07 master static $ bridge fdb add dev swp0 00:01:02:03:04:07 master static RTNETLINK answers: File exists
However, the same thing cannot be said about the bridge bypass operations:
$ bridge fdb add dev swp0 00:01:02:03:04:07 $ bridge fdb add dev swp0 00:01:02:03:04:07 $ bridge fdb add dev swp0 00:01:02:03:04:07 $ bridge fdb add dev swp0 00:01:02:03:04:07 $ echo $? 0
But one 'bridge fdb del' is enough to remove the entry, no matter how many times it was added.
The bridge bypass operations are impossible to maintain in these circumstances and lack of support for reference counting the cross-chip notifiers is holding us back from making further progress, so just drop support for them. The only way left for users to install static bridge FDB entries is the proper one, using the "master static" flags.
--- net/dsa/slave.c | 23 ----------------------- 1 file changed, 23 deletions(-)
net/dsa/slave.c +0 -23
@@ -1651,27 +1651,6 @@ static const struct ethtool_ops dsa_slave_ethtool_ops = { .self_test = dsa_slave_net_selftest, }; -/* legacy way, bypassing the bridge *****************************************/ -static int dsa_legacy_fdb_add (struct ndmsg *ndm,struct nlattr *tb[], -struct net_device *dev, -const unsigned char *addr,u16 vid, -u16 flags, -struct netlink_ext_ack *extack) -{ -struct dsa_port *dp =dsa_slave_to_port (dev); - -return dsa_port_fdb_add (dp, addr, vid); -} - -static int dsa_legacy_fdb_del (struct ndmsg *ndm,struct nlattr *tb[], -struct net_device *dev, -const unsigned char *addr,u16 vid) -{ -struct dsa_port *dp =dsa_slave_to_port (dev); - -return dsa_port_fdb_del (dp, addr, vid); -} -static struct devlink_port *dsa_slave_get_devlink_port (struct net_device *dev) {struct dsa_port *dp =dsa_slave_to_port (dev);
@@ -1713,8 +1692,6 @@ static const struct net_device_ops dsa_slave_netdev_ops = { .ndo_change_rx_flags = dsa_slave_change_rx_flags, .ndo_set_rx_mode = dsa_slave_set_rx_mode, .ndo_set_mac_address = dsa_slave_set_mac_address, - .ndo_fdb_add = dsa_legacy_fdb_add, - .ndo_fdb_del = dsa_legacy_fdb_del, .ndo_fdb_dump = dsa_slave_fdb_dump, .ndo_do_ioctl = dsa_slave_ioctl, .ndo_get_iflink = dsa_slave_get_iflink,
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 5/15 net: dsa: introduce dsa_is_upstream_port and dsa_switch_is_upstream_of
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
In preparation for the new cross-chip notifiers for host addresses, let's introduce some more topology helpers which we are going to use to discern switches that are in our path towards the dedicated CPU port from switches that aren't.
--- include/net/dsa.h | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
include/net/dsa.h +26 -0
@@ -491,6 +491,32 @@ static inline unsigned int dsa_upstream_port(struct dsa_switch *ds, int port)return dsa_towards_port (ds, cpu_dp->ds->index, cpu_dp->index); } +/* Return true if this is the local port used to reach the CPU port */ +static inline bool dsa_is_upstream_port (struct dsa_switch *ds,int port) +{ +if (dsa_is_unused_port (ds, port)) +return false; + +return port ==dsa_upstream_port (ds, port); +} + +/* Return true if @upstream_ds is an upstream switch of @downstream_ds, meaning +* that the routing port from @downstream_ds to @upstream_ds is also the port +* which @downstream_ds uses to reach its dedicated CPU. +*/ +static inline bool dsa_switch_is_upstream_of (struct dsa_switch *upstream_ds, +struct dsa_switch *downstream_ds) +{ +int routing_port; + +if (upstream_ds == downstream_ds) +return true; + + routing_port =dsa_routing_port (downstream_ds, upstream_ds->index); + +return dsa_is_upstream_port (downstream_ds, routing_port); +} +static inline bool dsa_port_is_vlan_filtering (const struct dsa_port *dp) {const struct dsa_switch *ds = dp->ds;
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 6/15 net: dsa: introduce a separate cross-chip notifier type for host MDBs
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
Commit abd49535c380 ("net: dsa: execute dsa_switch_mdb_add only for routing port in cross-chip topologies") does a surprisingly good job even for the SWITCHDEV_OBJ_ID_HOST_MDB use case, where DSA simply translates a switchdev object received on dp into a cross-chip notifier for dp->cpu_dp.
To visualize how that works, imagine the daisy chain topology below and consider a SWITCHDEV_OBJ_ID_HOST_MDB object emitted on sw2p0. How does the cross-chip notifier know to match on all the right ports (sw0p4, the dedicated CPU port, sw1p4, an upstream DSA link, and sw2p4, another upstream DSA link)?
|
sw0p0 sw0p1 sw0p2 sw0p3 sw0p4
[ user ] [ user ] [ user ] [ dsa ] [ cpu ]
[ ] [ ] [ ] [ ] [ x ]
|
+---------+
|
sw1p0 sw1p1 sw1p2 sw1p3 sw1p4
[ user ] [ user ] [ user ] [ dsa ] [ dsa ]
[ ] [ ] [ ] [ ] [ x ]
|
+---------+
|
sw2p0 sw2p1 sw2p2 sw2p3 sw2p4
[ user ] [ user ] [ user ] [ user ] [ dsa ]
[ ] [ ] [ ] [ ] [ x ]
The answer is simple: the dedicated CPU port of sw2p0 is sw0p4, and dsa_routing_port returns the upstream port for all switches.
That is fine, but there are other topologies where this does not work as well. There are trees with "H" topologies in the wild, where there are 2 or more switches with DSA links between them, but every switch has its dedicated CPU port. For these topologies, it seems stupid for the neighbor switches to install an MDB entry on the routing port, since these multicast addresses are fundamentally different than the usual ones we support (and that is the justification for this patch, to introduce the concept of a termination plane multicast MAC address, as opposed to a forwarding plane multicast MAC address).
For example, when a SWITCHDEV_OBJ_ID_HOST_MDB would get added to sw0p0, without this patch, it would get treated as a regular port MDB on sw0p2 and it would match on the ports below (including the sw1p3 routing port).
| |
sw0p0 sw0p1 sw0p2 sw0p3 sw1p3 sw1p2 sw1p1 sw1p0
[ user ] [ user ] [ cpu ] [ dsa ] [ dsa ] [ cpu ] [ user ] [ user ]
[ ] [ ] [ x ] [ ] ---- [ x ] [ ] [ ] [ ]With the patch, the host MDB notifier on sw0p0 matches only on the local switch, which is what we want for a termination plane address.
| |
sw0p0 sw0p1 sw0p2 sw0p3 sw1p3 sw1p2 sw1p1 sw1p0
[ user ] [ user ] [ cpu ] [ dsa ] [ dsa ] [ cpu ] [ user ] [ user ]
[ ] [ ] [ x ] [ ] ---- [ ] [ ] [ ] [ ]Name this new matching function "dsa_switch_host_address_match" since we will be reusing it soon for host FDB entries as well.
--- net/dsa/dsa_priv.h | 6 +++++ net/dsa/port.c | 24 ++++++++++++++++++ net/dsa/slave.c | 10 ++------ net/dsa/switch.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 95 insertions(+), 8 deletions(-)
net/dsa/dsa_priv.h +6 -0
@@ -27,6 +27,8 @@ enum {DSA_NOTIFIER_LAG_LEAVE ,DSA_NOTIFIER_MDB_ADD ,DSA_NOTIFIER_MDB_DEL , +DSA_NOTIFIER_HOST_MDB_ADD , +DSA_NOTIFIER_HOST_MDB_DEL ,DSA_NOTIFIER_VLAN_ADD ,DSA_NOTIFIER_VLAN_DEL , DSA_NOTIFIER_MTU,
@@ -214,6 +216,10 @@ int dsa_port_mdb_add(const struct dsa_port *dp, const struct switchdev_obj_port_mdb *mdb);int dsa_port_mdb_del (const struct dsa_port *dp,const struct switchdev_obj_port_mdb *mdb); +int dsa_port_host_mdb_add (const struct dsa_port *dp, +const struct switchdev_obj_port_mdb *mdb); +int dsa_port_host_mdb_del (const struct dsa_port *dp, +const struct switchdev_obj_port_mdb *mdb);int dsa_port_pre_bridge_flags (const struct dsa_port *dp,struct switchdev_brport_flags flags,struct netlink_ext_ack *extack);
net/dsa/port.c +24 -0
@@ -681,6 +681,30 @@ int dsa_port_mdb_del(const struct dsa_port *dp,return dsa_port_notify (dp,DSA_NOTIFIER_MDB_DEL , &info); } +int dsa_port_host_mdb_add (const struct dsa_port *dp, +const struct switchdev_obj_port_mdb *mdb) +{ +struct dsa_notifier_mdb_info info = { + .sw_index = dp->ds->index, + .port = dp->index, + .mdb = mdb, + }; + +return dsa_port_notify (dp,DSA_NOTIFIER_HOST_MDB_ADD , &info); +} + +int dsa_port_host_mdb_del (const struct dsa_port *dp, +const struct switchdev_obj_port_mdb *mdb) +{ +struct dsa_notifier_mdb_info info = { + .sw_index = dp->ds->index, + .port = dp->index, + .mdb = mdb, + }; + +return dsa_port_notify (dp,DSA_NOTIFIER_HOST_MDB_DEL , &info); +} +int dsa_port_vlan_add (struct dsa_port *dp,const struct switchdev_obj_port_vlan *vlan,struct netlink_ext_ack *extack)
net/dsa/slave.c +2 -8
@@ -418,10 +418,7 @@ static int dsa_slave_port_obj_add(struct net_device *dev, const void *ctx,if (!dsa_port_offloads_bridge (dp, obj->orig_dev))return -EOPNOTSUPP ; -/* DSA can directly translate this to a normal MDB add, -* but on the CPU port. -*/ - err =dsa_port_mdb_add (dp->cpu_dp,SWITCHDEV_OBJ_PORT_MDB (obj)); + err =dsa_port_host_mdb_add (dp,SWITCHDEV_OBJ_PORT_MDB (obj));break ;case SWITCHDEV_OBJ_ID_PORT_VLAN :if (!dsa_port_offloads_bridge_port (dp, obj->orig_dev))
@@ -495,10 +492,7 @@ static int dsa_slave_port_obj_del(struct net_device *dev, const void *ctx,if (!dsa_port_offloads_bridge (dp, obj->orig_dev))return -EOPNOTSUPP ; -/* DSA can directly translate this to a normal MDB add, -* but on the CPU port. -*/ - err =dsa_port_mdb_del (dp->cpu_dp,SWITCHDEV_OBJ_PORT_MDB (obj)); + err =dsa_port_host_mdb_del (dp,SWITCHDEV_OBJ_PORT_MDB (obj));break ;case SWITCHDEV_OBJ_ID_PORT_VLAN :if (!dsa_port_offloads_bridge_port (dp, obj->orig_dev))
net/dsa/switch.c +63 -0
81 lines not on this page · raw message
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 7/15 net: dsa: reference count the MDB entries at the cross-chip notifier level
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
Ever since the cross-chip notifiers were introduced, the design was meant to be simplistic and just get the job done without worrying too much about dangling resources left behind.
For example, somebody installs an MDB entry on sw0p0 in this daisy chain topology. It gets installed using ds->ops->port_mdb_add() on sw0p0, sw1p4 and sw2p4.
|
sw0p0 sw0p1 sw0p2 sw0p3 sw0p4
[ user ] [ user ] [ user ] [ dsa ] [ cpu ]
[ x ] [ ] [ ] [ ] [ ]
|
+---------+
|
sw1p0 sw1p1 sw1p2 sw1p3 sw1p4
[ user ] [ user ] [ user ] [ dsa ] [ dsa ]
[ ] [ ] [ ] [ ] [ x ]
|
+---------+
|
sw2p0 sw2p1 sw2p2 sw2p3 sw2p4
[ user ] [ user ] [ user ] [ user ] [ dsa ]
[ ] [ ] [ ] [ ] [ x ]
Then the same person deletes that MDB entry. The cross-chip notifier for deletion only matches sw0p0:
|
sw0p0 sw0p1 sw0p2 sw0p3 sw0p4
[ user ] [ user ] [ user ] [ dsa ] [ cpu ]
[ x ] [ ] [ ] [ ] [ ]
|
+---------+
|
sw1p0 sw1p1 sw1p2 sw1p3 sw1p4
[ user ] [ user ] [ user ] [ dsa ] [ dsa ]
[ ] [ ] [ ] [ ] [ ]
|
+---------+
|
sw2p0 sw2p1 sw2p2 sw2p3 sw2p4
[ user ] [ user ] [ user ] [ user ] [ dsa ]
[ ] [ ] [ ] [ ] [ ]
Why?
Because the DSA links are 'trunk' ports, if we just go ahead and delete the MDB from sw1p4 and sw2p4 directly, we might delete those multicast entries when they are still needed. Just consider the fact that somebody does:
- add a multicast MAC address towards sw0p0 [ via the cross-chip notifiers it gets installed on the DSA links too ]
- add the same multicast MAC address towards sw0p1 (another port of that same switch)
- delete the same multicast MAC address from sw0p0.
At this point, if we deleted the MAC address from the DSA links, it would be flooded, even though there is still an entry on switch 0 which needs it not to.
So that is why deletions only match the targeted source port and nothing on DSA links. Of course, dangling resources means that the hardware tables will eventually run out given enough additions/removals, but hey, at least it's simple.
But there is a bigger concern which needs to be addressed, and that is our support for SWITCHDEV_OBJ_ID_HOST_MDB. DSA simply translates such an object into a dsa_port_host_mdb_add() which ends up as ds->ops->port_mdb_add() on the upstream port, and a similar thing happens on deletion:dsa_port_host_mdb_del() will trigger ds->ops->port_mdb_del() on the upstream port.
When there are 2 VLAN-unaware bridges spanning the same switch (which is a use case DSA proudly supports), each bridge will install its own SWITCHDEV_OBJ_ID_HOST_MDB entries. But upon deletion, DSA goes ahead and emits a DSA_NOTIFIER_MDB_DEL for dp->cpu_dp, which is shared between the user ports enslaved to br0 and the user ports enslaved to br1. Not good. The host-trapped multicast addresses installed by br1 will be deleted when any state changes in br0 (IGMP timers expire, or ports leave, etc).
To avoid this, we could of course go the route of the zero-sum game and delete the DSA_NOTIFIER_MDB_DEL call for dp->cpu_dp. But the better design is to just admit that on shared ports like DSA links and CPU ports, we should be reference counting calls, even if this consumes some dynamic memory which DSA has traditionally avoided. On the flip side, the hardware tables of switches are limited in size, so it would be good if the OS managed them properly instead of having them eventually overflow.
To address the memory usage concern, we only apply the refcounting of MDB entries on ports that are really shared (CPU ports and DSA links) and not on user ports. In a typical single-switch setup, this means only the CPU port (and the host MDB entries are not that many, really).
The name of the newly introduced data structures (dsa_mac_addr) is chosen in such a way that will be reusable for host FDB entries (next patch).
With this change, we can finally have the same matching logic for the MDB additions and deletions, as well as for their host-trapped variants.
--- include/net/dsa.h | 12 ++++++ net/dsa/dsa2.c | 8 ++++ net/dsa/switch.c | 104 ++++++++++++++++++++++++++++++++++++++++++---- 3 files changed, 115 insertions(+), 9 deletions(-)
include/net/dsa.h +12 -0
@@ -285,6 +285,11 @@ struct dsa_port {*/ const struct dsa_netdevice_ops *netdev_ops; +/* List of MAC addresses that must be forwarded on this port. +* These are only valid on CPU ports and DSA links. +*/ +struct list_head mdbs; +bool setup; };
@@ -299,6 +304,13 @@ struct dsa_link {struct list_head list; }; +struct dsa_mac_addr { +unsigned char addr[ETH_ALEN ]; +u16 vid; +refcount_t refcount; +struct list_head list; +}; +struct dsa_switch {bool setup;
net/dsa/dsa2.c +8 -0
@@ -348,6 +348,8 @@ static int dsa_port_setup(struct dsa_port *dp)if (dp->setup)return 0 ; +INIT_LIST_HEAD (&dp->mdbs); +switch (dp->type) {case DSA_PORT_TYPE_UNUSED :dsa_port_disable (dp);
@@ -443,6 +445,7 @@ static int dsa_port_devlink_setup(struct dsa_port *dp)static void dsa_port_teardown (struct dsa_port *dp) {struct devlink_port *dlp = &dp->devlink_port; +struct dsa_mac_addr *a, *tmp;if (!dp->setup)return ;
@@ -468,6 +471,11 @@ static void dsa_port_teardown(struct dsa_port *dp)break ; } +list_for_each_entry_safe (a, tmp, &dp->mdbs, list) { +list_del (&a->list); +kfree (a); + } + dp->setup = false; }
net/dsa/switch.c +95 -9
140 lines not on this page · raw message
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 8/15 net: dsa: introduce a separate cross-chip notifier type for host FDBs
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
DSA treats some bridge FDB entries by trapping them to the CPU port. Currently, the only class of such entries are FDB addresses learnt by the software bridge on a foreign interface. However there are many more to be added:
- FDB entries with the is_local flag (for termination) added by the bridge on the user ports (typically containing the MAC address of the bridge port)
- FDB entries pointing towards the bridge net device (for termination). Typically these contain the MAC address of the bridge net device.
- Static FDB entries installed on a foreign interface that is in the same bridge with a DSA user port.
The reason why a separate cross-chip notifier for host FDBs is justified compared to normal FDBs is the same as in the case of host MDBs: the cross-chip notifier matching function in switch.c should avoid installing these entries on routing ports that route towards the targeted switch, but not towards the CPU. This is required in order to have proper support for H-like multi-chip topologies.
--- net/dsa/dsa_priv.h | 7 +++++++ net/dsa/port.c | 26 ++++++++++++++++++++++++++ net/dsa/slave.c | 21 ++++++++++++++++----- net/dsa/switch.c | 41 +++++++++++++++++++++++++++++++++++++++++ 4 files changed, 90 insertions(+), 5 deletions(-)
net/dsa/dsa_priv.h +7 -0
@@ -20,6 +20,8 @@ enum {DSA_NOTIFIER_BRIDGE_LEAVE ,DSA_NOTIFIER_FDB_ADD ,DSA_NOTIFIER_FDB_DEL , +DSA_NOTIFIER_HOST_FDB_ADD , +DSA_NOTIFIER_HOST_FDB_DEL ,DSA_NOTIFIER_HSR_JOIN ,DSA_NOTIFIER_HSR_LEAVE , DSA_NOTIFIER_LAG_CHANGE,
@@ -121,6 +123,7 @@ struct dsa_switchdev_event_work {*/ unsigned char addr[ETH_ALEN ];u16 vid; +bool host_addr; };/* DSA_NOTIFIER_HSR_* */
@@ -211,6 +214,10 @@ int dsa_port_fdb_add(struct dsa_port *dp, const unsigned char *addr, u16 vid);int dsa_port_fdb_del (struct dsa_port *dp,const unsigned char *addr,u16 vid); +int dsa_port_host_fdb_add (struct dsa_port *dp,const unsigned char *addr, +u16 vid); +int dsa_port_host_fdb_del (struct dsa_port *dp,const unsigned char *addr, +u16 vid);int dsa_port_fdb_dump (struct dsa_port *dp,dsa_fdb_dump_cb_t *cb,void *data);int dsa_port_mdb_add (const struct dsa_port *dp,const struct switchdev_obj_port_mdb *mdb);
net/dsa/port.c +26 -0
@@ -646,6 +646,32 @@ int dsa_port_fdb_del(struct dsa_port *dp, const unsigned char *addr,return dsa_port_notify (dp,DSA_NOTIFIER_FDB_DEL , &info); } +int dsa_port_host_fdb_add (struct dsa_port *dp,const unsigned char *addr, +u16 vid) +{ +struct dsa_notifier_fdb_info info = { + .sw_index = dp->ds->index, + .port = dp->index, + .addr = addr, + .vid = vid, + }; + +return dsa_port_notify (dp,DSA_NOTIFIER_HOST_FDB_ADD , &info); +} + +int dsa_port_host_fdb_del (struct dsa_port *dp,const unsigned char *addr, +u16 vid) +{ +struct dsa_notifier_fdb_info info = { + .sw_index = dp->ds->index, + .port = dp->index, + .addr = addr, + .vid = vid, + }; + +return dsa_port_notify (dp,DSA_NOTIFIER_HOST_FDB_DEL , &info); +} +int dsa_port_fdb_dump (struct dsa_port *dp,dsa_fdb_dump_cb_t *cb,void *data) {struct dsa_switch *ds = dp->ds;
net/dsa/slave.c +16 -5
@@ -2315,8 +2315,12 @@ static void dsa_slave_switchdev_event_work(struct work_struct *work)rtnl_lock ();switch (switchdev_work->event) {case SWITCHDEV_FDB_ADD_TO_DEVICE : - err =dsa_port_fdb_add (dp, switchdev_work->addr, - switchdev_work->vid); +if (switchdev_work->host_addr) + err =dsa_port_host_fdb_add (dp, switchdev_work->addr, + switchdev_work->vid); +else + err =dsa_port_fdb_add (dp, switchdev_work->addr, + switchdev_work->vid);if (err) { dev_err(ds->dev, "port %d failed to add %pM vid %d to fdb: %d\n",
@@ -2328,8 +2332,12 @@ static void dsa_slave_switchdev_event_work(struct work_struct *work)break ;case SWITCHDEV_FDB_DEL_TO_DEVICE : - err =dsa_port_fdb_del (dp, switchdev_work->addr, - switchdev_work->vid); +if (switchdev_work->host_addr) + err =dsa_port_host_fdb_del (dp, switchdev_work->addr, + switchdev_work->vid); +else + err =dsa_port_fdb_del (dp, switchdev_work->addr, + switchdev_work->vid);if (err) { dev_err(ds->dev, "port %d failed to delete %pM vid %d from fdb: %d\n",
@@ -2375,6 +2383,7 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused,struct net_device *dev =switchdev_notifier_info_to_dev (ptr);const struct switchdev_notifier_fdb_info *fdb_info;struct dsa_switchdev_event_work *switchdev_work; +bool host_addr = false;struct dsa_port *dp;int err;
@@ -2412,7 +2421,8 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused,if (!p)return NOTIFY_DONE ; - dp = p->dp->cpu_dp; + dp = p->dp; + host_addr = true;if (!dp->ds->assisted_learning_on_cpu_port)return NOTIFY_DONE ;
@@ -2442,6 +2452,7 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused,ether_addr_copy (switchdev_work->addr, fdb_info->addr); switchdev_work->vid = fdb_info->vid; + switchdev_work->host_addr = host_addr;/* Hold a reference on the slave for dsa_fdb_offload_notify */ if (dsa_is_user_port (dp->ds, dp->index))
net/dsa/switch.c +41 -0
53 lines not on this page · raw message
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 9/15 net: dsa: reference count the FDB addresses at the cross-chip notifier level
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
The same concerns expressed for host MDB entries are valid for host FDBs just as well:
- in the case of multiple bridges spanning the same switch chip, deleting a host FDB entry that belongs to one bridge will result in breakage to the other bridge
- not deleting FDB entries across DSA links means that the switch's hardware tables will eventually run out, given enough wear&tear
So do the same thing and introduce reference counting for CPU ports and DSA links using the same data structures as we have for MDB entries.
--- include/net/dsa.h | 1 + net/dsa/dsa2.c | 6 ++++ net/dsa/switch.c | 88 +++++++++++++++++++++++++++++++++++++++++++---- 3 files changed, 88 insertions(+), 7 deletions(-)
include/net/dsa.h +1 -0
@@ -288,6 +288,7 @@ struct dsa_port {/* List of MAC addresses that must be forwarded on this port. * These are only valid on CPU ports and DSA links. */ +struct list_head fdbs;struct list_head mdbs;bool setup;
net/dsa/dsa2.c +6 -0
@@ -348,6 +348,7 @@ static int dsa_port_setup(struct dsa_port *dp)if (dp->setup)return 0 ; +INIT_LIST_HEAD (&dp->fdbs);INIT_LIST_HEAD (&dp->mdbs);switch (dp->type) {
@@ -471,6 +472,11 @@ static void dsa_port_teardown(struct dsa_port *dp)break ; } +list_for_each_entry_safe (a, tmp, &dp->fdbs, list) { +list_del (&a->list); +kfree (a); + } +list_for_each_entry_safe (a, tmp, &dp->mdbs, list) {list_del (&a->list);kfree (a);
net/dsa/switch.c +81 -7
122 lines not on this page · raw message
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 10/15 net: dsa: install the host MDB and FDB entries in the master's RX filter
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
If the DSA master implements strict address filtering, then the unicast and multicast addresses kept by the DSA CPU ports should be synchronized with the address lists of the DSA master.
Note that we want the synchronization of the master's address lists even if the DSA switch doesn't support unicast/multicast database operations, on the premises that the packets will be flooded to the CPU in that case, and we should still instruct the master to receive them.
--- net/dsa/port.c | 32 ++++++++++++++++++++++++++++---- 1 file changed, 28 insertions(+), 4 deletions(-)
net/dsa/port.c +28 -4
@@ -655,8 +655,14 @@ int dsa_port_host_fdb_add(struct dsa_port *dp, const unsigned char *addr, .addr = addr, .vid = vid, }; +struct dsa_port *cpu_dp = dp->cpu_dp; +int err; + + err =dsa_port_notify (dp,DSA_NOTIFIER_HOST_FDB_ADD , &info); +if (err) +return err; -return dsa_port_notify (dp,DSA_NOTIFIER_HOST_FDB_ADD , &info); +return dev_uc_add (cpu_dp->master, addr); } int dsa_port_host_fdb_del(struct dsa_port *dp, const unsigned char *addr,
@@ -668,8 +674,14 @@ int dsa_port_host_fdb_del(struct dsa_port *dp, const unsigned char *addr, .addr = addr, .vid = vid, }; +struct dsa_port *cpu_dp = dp->cpu_dp; +int err; + + err =dsa_port_notify (dp,DSA_NOTIFIER_HOST_FDB_DEL , &info); +if (err) +return err; -return dsa_port_notify (dp,DSA_NOTIFIER_HOST_FDB_DEL , &info); +return dev_uc_del (cpu_dp->master, addr); }int dsa_port_fdb_dump (struct dsa_port *dp,dsa_fdb_dump_cb_t *cb,void *data)
@@ -715,8 +727,14 @@ int dsa_port_host_mdb_add(const struct dsa_port *dp, .port = dp->index, .mdb = mdb, }; +struct dsa_port *cpu_dp = dp->cpu_dp; +int err; + + err =dsa_port_notify (dp,DSA_NOTIFIER_HOST_MDB_ADD , &info); +if (err) +return err; -return dsa_port_notify (dp,DSA_NOTIFIER_HOST_MDB_ADD , &info); +return dev_mc_add (cpu_dp->master, mdb->addr); } int dsa_port_host_mdb_del(const struct dsa_port *dp,
@@ -727,8 +745,14 @@ int dsa_port_host_mdb_del(const struct dsa_port *dp, .port = dp->index, .mdb = mdb, }; +struct dsa_port *cpu_dp = dp->cpu_dp; +int err; + + err =dsa_port_notify (dp,DSA_NOTIFIER_HOST_MDB_DEL , &info); +if (err) +return err; -return dsa_port_notify (dp,DSA_NOTIFIER_HOST_MDB_DEL , &info); +return dev_mc_del (cpu_dp->master, mdb->addr); } int dsa_port_vlan_add(struct dsa_port *dp,
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 11/15 net: dsa: sync static FDB entries on foreign interfaces to hardware
In reply to Vladimir OlteanFrom: Tobias Waldekranz <[email protected]>
Reuse the "assisted_learning_on_cpu_port" functionality to always add entries for user-configured entries on foreign interfaces, even if assisted_learning_on_cpu_port is not enabled. E.g. in this situation:
br0
/ \
swp0 dummy0
$ bridge fdb add 02:00:de:ad:00:01 dev dummy0 vlan 1 master static
Results in DSA adding an entry in the hardware FDB, pointing this address towards the CPU port.
The same is true for entries added to the bridge itself, e.g:
$ bridge fdb add 02:00:de:ad:00:01 dev br0 vlan 1 self local
--- net/dsa/slave.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
net/dsa/slave.c +8 -4
@@ -2403,9 +2403,12 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused, dp =dsa_slave_to_port (dev); }else { -/* Snoop addresses learnt on foreign interfaces -* bridged with us, for switches that don't -* automatically learn SA from CPU-injected traffic +/* Snoop addresses added to foreign interfaces +* bridged with us, or the bridge +* itself. Dynamically learned addresses can +* also be added for switches that don't +* automatically learn SA from CPU-injected +* traffic. */ struct net_device *br_dev;struct dsa_slave_priv *p;
@@ -2424,7 +2427,8 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused, dp = p->dp; host_addr = true; -if (!dp->ds->assisted_learning_on_cpu_port) +if (!fdb_info->added_by_user && + !dp->ds->assisted_learning_on_cpu_port)return NOTIFY_DONE ;/* When the bridge learns an address on an offloaded
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 12/15 net: dsa: include bridge addresses which are local in the host fdb list
In reply to Vladimir OlteanFrom: Tobias Waldekranz <[email protected]>
The bridge automatically creates local (not forwarded) fdb entries pointing towards physical ports with their interface MAC addresses. For switchdev, the significance of these fdb entries is the exact opposite of that of non-local entries: instead of sending these frame outwards, we must send them inwards (towards the host).
NOTE: The bridge's own MAC address is also "local". If that address is not shared with any port, the bridge's MAC is not be added by this functionality - but the following commit takes care of that case.
NOTE 2: We mark these addresses as host-filtered regardless of the value of ds->assisted_learning_on_cpu_port. This is because, as opposed to the speculative logic done for dynamic address learning on foreign interfaces, the local FDB entries are rather fixed, so there isn't any risk of them migrating from one bridge port to another.
--- net/dsa/slave.c | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-)
net/dsa/slave.c +13 -5
@@ -2398,10 +2398,12 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused, fdb_info = ptr;if (dsa_slave_dev_check (dev)) { -if (!fdb_info->added_by_user || fdb_info->is_local) -return NOTIFY_OK ; - dp =dsa_slave_to_port (dev); + +if (fdb_info->is_local) + host_addr = true; +else if (!fdb_info->added_by_user) +return NOTIFY_OK ; }else {/* Snoop addresses added to foreign interfaces * bridged with us, or the bridge
@@ -2425,9 +2427,15 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused,return NOTIFY_DONE ; dp = p->dp; - host_addr = true; + host_addr = fdb_info->is_local; -if (!fdb_info->added_by_user && +/* FDB entries learned by the software bridge should +* be installed as host addresses only if the driver +* requests assisted learning. +* On the other hand, FDB entries for local termination +* should always be installed. +*/ +if (!fdb_info->added_by_user && !fdb_info->is_local && !dp->ds->assisted_learning_on_cpu_port)return NOTIFY_DONE ;
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 13/15 net: dsa: include fdb entries pointing to bridge in the host fdb list
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
The bridge supports a legacy way of adding local (non-forwarded) FDB entries, which works on an individual port basis:
bridge fdb add dev swp0 00:01:02:03:04:05 master local
As well as a new way, added by Roopa Prabhu in commit 3741873b4f73 ("bridge: allow adding of fdb entries pointing to the bridge device"):
bridge fdb add dev br0 00:01:02:03:04:05 self local
The two commands are functionally equivalent, except that the first one produces an entry with fdb->dst == swp0, and the other an entry with fdb->dst == NULL. The confusing part, though, is that even if fdb->dst is swp0 for the 'local on port' entry, that destination is not used.
Nonetheless, the idea is that the bridge has reference counting for local entries, and local entries pointing towards the bridge are still 'as local' as local entries for a port.
The bridge adds the MAC addresses of the interfaces automatically as FDB entries with is_local=1. For the MAC address of the ports, fdb->dst will be equal to the port, and for the MAC address of the bridge, fdb->dst will point towards the bridge (i.e. be NULL). Therefore, if the MAC address of the bridge is not inherited from either of the physical ports, then we must explicitly catch local FDB entries emitted towards the br0, otherwise we'll miss the MAC address of the bridge (and, of course, any entry with 'bridge add dev br0 ... self local').
--- net/dsa/slave.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
net/dsa/slave.c +11 -2
@@ -2415,7 +2415,11 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused,struct net_device *br_dev;struct dsa_slave_priv *p; - br_dev =netdev_master_upper_dev_get_rcu (dev); +if (netif_is_bridge_master (dev)) + br_dev = dev; +else + br_dev =netdev_master_upper_dev_get_rcu (dev); +if (!br_dev)return NOTIFY_DONE ;
@@ -2443,8 +2447,13 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused,* LAG we don't want to send traffic to the CPU, the * other ports bridged with the LAG should be able to * autonomously forward towards it. +* On the other hand, if the address is local +* (therefore not learned) then we want to trap it to +* the CPU regardless of whether the interface it +* belongs to is offloaded or not. */ -if (dsa_tree_offloads_bridge_port (dp->ds->dst, dev)) +if (dsa_tree_offloads_bridge_port (dp->ds->dst, dev) && + !fdb_info->is_local)return NOTIFY_DONE ; }
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 14/15 net: dsa: ensure during dsa_fdb_offload_notify that dev_hold and dev_put are on the same dev
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
When
(a) "dev" is a bridge port which the DSA switch tree offloads, but is otherwise not a dsa slave (such as a LAG netdev), or
(b) "dev" is the bridge net device itself
then strange things happen to the dev_hold/dev_put pair:dsa_schedule_work() will still be called with a DSA port that offloads that netdev, but dev_hold() will be called on the non-DSA netdev. Then the "if" condition in dsa_slave_switchdev_event_work() does not pass, because "dev" is not a DSA netdev, so dev_put() is not called.
This results in the simple fact that we have a reference counting mismatch on the "dev" net device.
This can be seen when we add support for host addresses installed on the bridge net device.
ip link add br1 type bridge
ip link set br1 address 00:01:02:03:04:05
ip link set swp0 master br1
ip link del br1
[ 968.512278] unregister_netdevice: waiting for br1 to become free. Usage count = 5
It seems foolish to do penny pinching and not add the net_device pointer in the dsa_switchdev_event_work structure, so let's finally do that. As an added bonus, when we start offloading local entries pointing towards the bridge, these will now properly appear as 'offloaded' in 'bridge fdb' (this was not possible before, because 'dev' was assumed to only be a DSA net device):
00:01:02:03:04:05 dev br0 vlan 1 offload master br0 permanent 00:01:02:03:04:05 dev br0 offload master br0 permanent
--- net/dsa/dsa_priv.h | 1 + net/dsa/slave.c | 9 ++++----- 2 files changed, 5 insertions(+), 5 deletions(-)
net/dsa/dsa_priv.h +1 -0
@@ -116,6 +116,7 @@ struct dsa_notifier_mrp_ring_role_info {struct dsa_switchdev_event_work {struct dsa_switch *ds;int port; +struct net_device *dev;struct work_struct work;unsigned long event;/* Specific for SWITCHDEV_FDB_ADD_TO_DEVICE and
net/dsa/slave.c +4 -5
@@ -2349,9 +2349,8 @@ static void dsa_slave_switchdev_event_work(struct work_struct *work) }rtnl_unlock (); +dev_put (switchdev_work->dev);kfree (switchdev_work); -if (dsa_is_user_port (ds, dp->index)) -dev_put (dp->slave); } static int dsa_lower_dev_walk(struct net_device *lower_dev,
@@ -2469,15 +2468,15 @@ static int dsa_slave_switchdev_event(struct notifier_block *unused, switchdev_work->ds = dp->ds; switchdev_work->port = dp->index; switchdev_work->event = event; + switchdev_work->dev = dev;ether_addr_copy (switchdev_work->addr, fdb_info->addr); switchdev_work->vid = fdb_info->vid; switchdev_work->host_addr = host_addr; -/* Hold a reference on the slave for dsa_fdb_offload_notify */ -if (dsa_is_user_port (dp->ds, dp->index)) -dev_hold (dev); +/* Hold a reference for dsa_fdb_offload_notify */ +dev_hold (dev);dsa_schedule_work (&switchdev_work->work);break ;default :
Signature · 1 line
2.25.1
Vladimir Oltean
maintainerRFC PATCH v3 15/15 net: dsa: replay the local bridge FDB entries pointing to the bridge dev too
In reply to Vladimir OlteanFrom: Vladimir Oltean <[email protected]>
When we join a bridge that already has some local addresses pointing to itself, we do not get those notifications. Similarly, when we leave that bridge, we do not get notifications for the deletion of those entries. The only switchdev notifications we get are those of entries added while the DSA port is enslaved to the bridge.
This makes use cases such as the following work properly (with the number of additions and removals properly balanced):
ip link add br0 type bridge
ip link add br1 type bridge
ip link set br0 address 00:01:02:03:04:05
ip link set br1 address 00:01:02:03:04:05
ip link set swp0 up
ip link set swp1 up
ip link set swp0 master br0
ip link set swp1 master br1
ip link set br0 up
ip link set br1 up
ip link del br1 # 00:01:02:03:04:05 still installed on the CPU port ip link del br0 # 00:01:02:03:04:05 finally removed from the CPU port
--- net/dsa/port.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
net/dsa/port.c +12 -0
@@ -199,11 +199,17 @@ static int dsa_port_switchdev_sync(struct dsa_port *dp,if (err && err != -EOPNOTSUPP )return err; +/* Forwarding and termination FDB entries on the port */ err =br_fdb_replay (br, brport_dev, dp, true, &dsa_slave_switchdev_notifier);if (err && err != -EOPNOTSUPP )return err; +/* Termination FDB entries on the bridge itself */ + err =br_fdb_replay (br, br, dp, true, &dsa_slave_switchdev_notifier); +if (err && err != -EOPNOTSUPP ) +return err; + err =br_vlan_replay (br, brport_dev, dp, true, &dsa_slave_switchdev_blocking_notifier, extack);if (err && err != -EOPNOTSUPP )
@@ -225,11 +231,17 @@ static int dsa_port_switchdev_unsync_objs(struct dsa_port *dp,if (err && err != -EOPNOTSUPP )return err; +/* Forwarding and termination FDB entries on the port */ err =br_fdb_replay (br, brport_dev, dp, false, &dsa_slave_switchdev_notifier);if (err && err != -EOPNOTSUPP )return err; +/* Termination FDB entries on the bridge itself */ + err =br_fdb_replay (br, br, dp, false, &dsa_slave_switchdev_notifier); +if (err && err != -EOPNOTSUPP ) +return err; + err =br_vlan_replay (br, brport_dev, dp, false, &dsa_slave_switchdev_blocking_notifier, extack);if (err && err != -EOPNOTSUPP )
Signature · 1 line
2.25.1