aboutsummaryrefslogtreecommitdiffstats
path: root/net/core/lock_debug.c
diff options
context:
space:
mode:
authorJakub Kicinski <[email protected]>2025-04-10 02:13:46 +0000
committerJakub Kicinski <[email protected]>2025-04-10 02:13:46 +0000
commit330689f757a7b31794b9887788da679be2d03248 (patch)
treea0f4c231521833a366aeb012c1553fa7ea1991d6 /net/core/lock_debug.c
parentnet: remove cpu stall in txq_trans_update() (diff)
parentselftests: test_bridge_neigh_suppress: Test unicast ARP/NS with suppression (diff)
downloadkernel-330689f757a7b31794b9887788da679be2d03248.tar.gz
kernel-330689f757a7b31794b9887788da679be2d03248.zip
Merge branch 'bridge-prevent-unicast-arp-ns-packets-from-being-suppressed-by-bridge'
Amit Cohen says: ==================== bridge: Prevent unicast ARP/NS packets from being suppressed by bridge Currently, unicast ARP requests/NS packets are replied by bridge when suppression is enabled, then they are also forwarded, which results two replicas of ARP reply/NA - one from the bridge and second from the target. The purpose of ARP/ND suppression is to reduce flooding in the broadcast domain, which is not relevant for unicast packets. In addition, the use case of unicast ARP/NS is to poll a specific host, so it does not make sense to have the switch answer on behalf of the host. Forward ARP requests/NS packets and prevent the bridge from replying to them. Patch set overview: Patch #1 prevents unicast ARP/NS packets from being suppressed by bridge Patch #2 adds test cases for unicast ARP/NS with suppression enabled ==================== Link: https://patch.msgid.link/[email protected] Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'net/core/lock_debug.c')
0 files changed, 0 insertions, 0 deletions