diff options
author | 2021-06-24 18:06:05 +0200 | |
---|---|---|
committer | 2021-06-24 19:45:39 +0200 | |
commit | 4415db6ca85ae57830a83290388f2b9dfa5f237f (patch) | |
tree | 4aebaecb2b573bc46a658c3bada8b2385fe68638 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | nfp: Remove rcu_read_lock() around XDP program invocation (diff) | |
download | linux-dev-4415db6ca85ae57830a83290388f2b9dfa5f237f.tar.xz linux-dev-4415db6ca85ae57830a83290388f2b9dfa5f237f.zip |
qede: Remove rcu_read_lock() around XDP program invocation
The qede 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: Ariel Elior <aelior@marvell.com>
Cc: gr-everest-linux-l2@marvell.com
Link: https://lore.kernel.org/bpf/20210624160609.292325-16-toke@redhat.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions