summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-10-06 16:23:11 -0700
committerJakub Kicinski <kuba@kernel.org>2026-10-06 16:23:12 -0700
commit588003f74005bbe34cdb4a39f65312cd43cf6935 (patch)
treed19cdf804c8281bc4c71285f469ef4475fef6e7e /tools/perf/scripts/python
parenta463f55c791b96cfd12df8b10ea737d45c80bb18 (diff)
parentd3daa33c7af92e38f2274bbd2576f58bfbaf89e6 (diff)
downloadlinux-588003f74005bbe34cdb4a39f65312cd43cf6935.tar.gz
linux-588003f74005bbe34cdb4a39f65312cd43cf6935.zip
Merge branch 'ipv4-handle-nexthop-group-shrink-races'
Daehyeon Ko says: ==================== ipv4: handle nexthop group shrink races fib_info_num_path() and fib_info_nhc() can observe different RCU generations of a replaceable nexthop group. An indexed consumer can therefore accept an index from a larger group and receive NULL after a concurrent shrink. Patch 1 is unchanged from v1. Patch 2 addresses the analogous fib_dump_info_fnhe() race Ido identified. Auditing the remaining accessor pairs found the same issue in the RCU-only hardware-flag notification path, fixed by patch 3. Separate patches retain the correct Fixes tag for each concurrency boundary. ==================== Link: https://patch.msgid.link/cover.1790915964.git.4ncienth@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions