summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorToke Høiland-Jørgensen <toke@redhat.com>2021-06-24 19:06:06 +0300
committerDaniel Borkmann <daniel@iogearbox.net>2021-06-24 20:46:01 +0300
commit4eb14e3fc6197b7205069ed4e2b31eafa11a0697 (patch)
treea31ac8a2c2aa564c0f4f781edbc83aeeff7ed2e9 /tools/perf/scripts/python/export-to-postgresql.py
parent4415db6ca85ae57830a83290388f2b9dfa5f237f (diff)
downloadlinux-4eb14e3fc6197b7205069ed4e2b31eafa11a0697.tar.xz
sfc: Remove rcu_read_lock() around XDP program invocation
The sfc 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> Acked-by: Edward Cree <ecree.xilinx@gmail.com> Cc: Martin Habets <habetsm.xilinx@gmail.com> Link: https://lore.kernel.org/bpf/20210624160609.292325-17-toke@redhat.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions