diff options
author | Toke Høiland-Jørgensen <toke@redhat.com> | 2021-06-24 19:06:08 +0300 |
---|---|---|
committer | Daniel Borkmann <daniel@iogearbox.net> | 2021-06-24 20:46:25 +0300 |
commit | 2f1e432d339c5fed435adf521cae392755721050 (patch) | |
tree | 626683b2ed90859c4ac4edeb3153dd770aab2667 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 7b6ee873ff20c22af355661b241defa7f6ed7582 (diff) | |
download | linux-2f1e432d339c5fed435adf521cae392755721050.tar.xz |
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 <toke@redhat.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Jose Abreu <joabreu@synopsys.com>
Link: https://lore.kernel.org/bpf/20210624160609.292325-19-toke@redhat.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions