diff options
author | 2023-09-21 08:46:26 +0000 | |
---|---|---|
committer | 2023-10-01 16:29:06 +0100 | |
commit | 25563b581ba3a1f263a00e8c9a97f5e7363be6fd (patch) | |
tree | b3564a6168f019dd55288ea76dc481d2b2c04832 /tools/perf/scripts/python/stackcollapse.py | |
parent | Merge tag 'for-net-2023-09-20' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth (diff) | |
download | wireguard-linux-25563b581ba3a1f263a00e8c9a97f5e7363be6fd.tar.xz wireguard-linux-25563b581ba3a1f263a00e8c9a97f5e7363be6fd.zip |
net: fix possible store tearing in neigh_periodic_work()
While looking at a related syzbot report involving neigh_periodic_work(),
I found that I forgot to add an annotation when deleting an
RCU protected item from a list.
Readers use rcu_deference(*np), we need to use either
rcu_assign_pointer() or WRITE_ONCE() on writer side
to prevent store tearing.
I use rcu_assign_pointer() to have lockdep support,
this was the choice made in neigh_flush_dev().
Fixes: 767e97e1e0db ("neigh: RCU conversion of struct neighbour")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: David Ahern <dsahern@kernel.org>
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions