diff options
author | 2025-08-27 07:43:20 -0700 | |
---|---|---|
committer | 2025-08-27 07:43:20 -0700 | |
commit | ceb9515524046252c522b16f38881e8837ec0d91 (patch) | |
tree | 4fdf9fce70085fc267ea45c4982a6f101685766d /tools/perf/scripts/python | |
parent | net: hv_netvsc: fix loss of early receive events from host during channel open. (diff) | |
parent | net: rose: include node references in rose_neigh refcount (diff) | |
download | wireguard-linux-ceb9515524046252c522b16f38881e8837ec0d91.tar.xz wireguard-linux-ceb9515524046252c522b16f38881e8837ec0d91.zip |
Merge branch 'introduce-refcount_t-for-reference-counting-of-rose_neigh'
Takamitsu Iwai says:
====================
Introduce refcount_t for reference counting of rose_neigh
The current implementation of rose_neigh uses 'use' and 'count' field of
type unsigned short as a reference count. This approach lacks atomicity,
leading to potential race conditions. As a result, syzbot has reported
slab-use-after-free errors due to unintended removals.
This series introduces refcount_t for reference counting to ensure
atomicity and prevent race conditions. The patches are structured as
follows:
1. Refactor rose_remove_neigh() to separate removal and freeing operations
2. Convert 'use' field to refcount_t for appropriate reference counting
3. Include references from rose_node to 'use' field
These changes should resolve the reported slab-use-after-free issues and
improve the overall stability of the ROSE network layer.
v1: https://lore.kernel.org/20250820174707.83372-1-takamitz@amazon.co.jp
====================
Link: https://patch.msgid.link/20250823085857.47674-1-takamitz@amazon.co.jp
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions