diff options
| author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2021-06-29 16:06:58 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2021-06-29 19:46:23 +0200 |
| commit | 63c51453c82cddc27556233ff41041ea9fc49fe0 (patch) | |
| tree | 4299fdf57fa2a7d1c6b649089736321a1f1d7cc8 /fs/jbd2 | |
| parent | net: dsa: ensure during dsa_fdb_offload_notify that dev_hold and dev_put are ... (diff) | |
| download | linux-63c51453c82cddc27556233ff41041ea9fc49fe0.tar.xz linux-63c51453c82cddc27556233ff41041ea9fc49fe0.zip | |
net: dsa: replay the local bridge FDB entries pointing to the bridge dev too
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
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/jbd2')
0 files changed, 0 insertions, 0 deletions