diff options
| author |   Ido Schimmel <idosch@nvidia.com> | 2025-04-15 15:11:29 +0300 |
|---|---|---|
| committer |   Paolo Abeni <pabeni@redhat.com> | 2025-04-22 11:11:15 +0200 |
| commit | 804b09be09f8af4eda5346a72361459ba21fcf1b (patch) | |
| tree | 3d6a6b11aafa4c176d305ea601439b8e0a95eb72 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | Merge tag 'for-netdev' of https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next (diff) | |
| download | wireguard-linux-804b09be09f8af4eda5346a72361459ba21fcf1b.tar.xz wireguard-linux-804b09be09f8af4eda5346a72361459ba21fcf1b.zip | |
vxlan: Add RCU read-side critical sections in the Tx path
The Tx path does not run from an RCU read-side critical section which
makes the current lockless accesses to FDB entries invalid. As far as I
am aware, this has not been a problem in practice, but traces will be
generated once we transition the FDB lookup to rhashtable_lookup().
Add rcu_read_{lock,unlock}() around the handling of FDB entries in the
Tx path. Remove the RCU read-side critical section from vxlan_xmit_nh()
as now the function is always called from an RCU read-side critical
section.
Reviewed-by: Petr Machata <petrm@nvidia.com>
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Link: https://patch.msgid.link/20250415121143.345227-2-idosch@nvidia.com
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions