summaryrefslogtreecommitdiff
path: root/drivers/net/ethernet/netronome
diff options
context:
space:
mode:
authorToke Høiland-Jørgensen <toke@redhat.com>2021-06-24 19:06:03 +0300
committerDaniel Borkmann <daniel@iogearbox.net>2021-06-24 20:45:18 +0300
commitc4411b371c104e65efb531ebd4d8892c568e3a29 (patch)
tree861e042e7c0b005f802ace87d0418f6b57c3c219 /drivers/net/ethernet/netronome
parent959ad7ec066d9a61557ad6aedf77ea9b54c82df0 (diff)
downloadlinux-c4411b371c104e65efb531ebd4d8892c568e3a29.tar.xz
mlx4: Remove rcu_read_lock() around XDP program invocation
The mlx4 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. Also switch the RCU dereferences in the driver loop itself to the _bh variants. Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Reviewed-by: Tariq Toukan <tariqt@nvidia.com> Link: https://lore.kernel.org/bpf/20210624160609.292325-14-toke@redhat.com
Diffstat (limited to 'drivers/net/ethernet/netronome')
0 files changed, 0 insertions, 0 deletions