diff options
| author |   Ido Schimmel <idosch@nvidia.com> | 2025-04-15 15:11:32 +0300 |
|---|---|---|
| committer |   Paolo Abeni <pabeni@redhat.com> | 2025-04-22 11:11:15 +0200 |
| commit | ccc203b9a846c1d5262b5c60565ff79930c13477 (patch) | |
| tree | dce308eb98488776b8ca4a19c0a6669f9ee9839f /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | vxlan: Insert FDB into hash table in vxlan_fdb_create() (diff) | |
| download | wireguard-linux-ccc203b9a846c1d5262b5c60565ff79930c13477.tar.xz wireguard-linux-ccc203b9a846c1d5262b5c60565ff79930c13477.zip | |
vxlan: Unsplit default FDB entry creation and notification
Commit 0241b836732f ("vxlan: fix default fdb entry netlink notify
ordering during netdev create") split the creation of the default FDB
entry from its notification to avoid sending a RTM_NEWNEIGH notification
before RTM_NEWLINK.
Previous patches restructured the code so that the default FDB entry is
created after registering the VXLAN device and the notification about
the new entry immediately follows its creation.
Therefore, simplify the code and revert back to vxlan_fdb_update() which
takes care of both creating the FDB entry and notifying user space
about it.
Hold the FDB hash lock when calling vxlan_fdb_update() like it expects.
A subsequent patch will add a lockdep assertion to make sure this is
indeed the case.
Reviewed-by: Petr Machata <petrm@nvidia.com>
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Link: https://patch.msgid.link/20250415121143.345227-5-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