diff options
author | Toke Høiland-Jørgensen <[email protected]> | 2021-06-24 18:06:08 +0200 |
---|---|---|
committer | Daniel Borkmann <[email protected]> | 2021-06-24 19:46:25 +0200 |
commit | 2f1e432d339c5fed435adf521cae392755721050 (patch) | |
tree | 626683b2ed90859c4ac4edeb3153dd770aab2667 /scripts/gdb/linux/tasks.py | |
parent | 7b6ee873ff20c22af355661b241defa7f6ed7582 (diff) |
stmmac: Remove rcu_read_lock() around XDP program invocation
The stmmac driver has rcu_read_lock()/rcu_read_unlock() pairs around XDP
program invocations. However, the actual lifetime of the objects referred
by the XDP program invocation is longer, all the way through to the call to
xdp_do_flush(), making the scope of the rcu_read_lock() too small. This
turns out to be harmless because it all happens in a single NAPI poll
cycle (and thus under local_bh_disable()), but it makes the rcu_read_lock()
misleading.
Rather than extend the scope of the rcu_read_lock(), just get rid of it
entirely. With the addition of RCU annotations to the XDP_REDIRECT map
types that take bh execution into account, lockdep even understands this to
be safe, so there's really no reason to keep it around.
Signed-off-by: Toke Høiland-Jørgensen <[email protected]>
Signed-off-by: Daniel Borkmann <[email protected]>
Cc: Giuseppe Cavallaro <[email protected]>
Cc: Alexandre Torgue <[email protected]>
Cc: Jose Abreu <[email protected]>
Link: https://lore.kernel.org/bpf/[email protected]
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions