diff options
| author | Jakub Kicinski <[email protected]> | 2024-12-20 21:16:46 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2024-12-20 21:16:47 +0000 |
| commit | c1bc6d217858f7de7db01658f4b0d799bebc21ac (patch) | |
| tree | 47d22e55011913428c774c9bc91454e2b4049577 /tools/testing/selftests/net/lib/py/utils.py | |
| parent | inetpeer: avoid false sharing in inet_peer_xrlim_allow() (diff) | |
| parent | selftests: net: Add a VLAN bridge binding selftest (diff) | |
| download | kernel-c1bc6d217858f7de7db01658f4b0d799bebc21ac.tar.gz kernel-c1bc6d217858f7de7db01658f4b0d799bebc21ac.zip | |
Merge branch 'bridge-handle-changes-in-vlan_flag_bridge_binding'
Petr Machata says:
====================
bridge: Handle changes in VLAN_FLAG_BRIDGE_BINDING
When bridge binding is enabled on a VLAN netdevice, its link state should
track bridge ports that are members of the corresponding VLAN. This works
for a newly-added netdevices. However toggling the option does not have the
effect of enabling or disabling the behavior as appropriate.
In this patchset, have bridge react to bridge_binding toggles on VLAN
uppers.
There has been another attempt at supporting this behavior in 2022 by
Sevinj Aghayeva [0]. A discussion ensued that informed how this new
patchset is constructed, namely that the logic is in the bridge as opposed
to the 8021q driver, and the bridge reacts to NETDEV_CHANGE events on the
8021q upper.
Patches #1 and #2 contain the implementation, patches #3 and #4 a
selftest.
[0] https://lore.kernel.org/netdev/[email protected]/
====================
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/testing/selftests/net/lib/py/utils.py')
0 files changed, 0 insertions, 0 deletions