diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-08-20 14:23:07 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-08-20 14:23:08 -0700 |
| commit | e264c048709469096f3927fcd35a2c45f9e38eb8 (patch) | |
| tree | 8b174d630b3b1b0276d7e550d9ff9c4805edea02 /tools/perf/scripts/python | |
| parent | 5ee0ceddc7785c6dcf4a8107fef01f0414a354f4 (diff) | |
| parent | b824059a673b2283e78c7aae2c7d257aad7f0e1d (diff) | |
| download | linux-e264c048709469096f3927fcd35a2c45f9e38eb8.tar.gz linux-e264c048709469096f3927fcd35a2c45f9e38eb8.zip | |
Merge branch 'bridge-vxlan-fix-reading-neigh-ha-without-synchronization'
Nikolay Aleksandrov says:
====================
bridge/vxlan: fix reading neigh ha without synchronization
Neigh ha address must be read using the seqlock to get a stable snapshot.
Both the bridge and vxlan read it directly and can see partial updates.
I reproduced both issues with running neigh updates and exercising these
paths in parallel and saw partial addresses, e.g. updating between
neigh A: 02:00:00:00:00:00 neigh B: fe:ff:ff:ff:ff:ff was able to observe
02:00:ff:ff:ff:ff and fe:ff:00:00:00:00 in packets. Noticed this initially
in the bridge, then checked vxlan and its arp/neigh_reduce functions have
the same bug, route_shortcircuit is doing the right thing already.
====================
Link: https://patch.msgid.link/20260818150756.890025-1-razor@blackwall.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions