diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-06-04 08:47:48 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-06-04 08:47:48 -0700 |
| commit | 05ef0afa1bd63ae36a594e9b8e92057660e3b3a2 (patch) | |
| tree | c785e68b6c90a0006d56789889efcfa3d866d889 /scripts/objdiff | |
| parent | ab1ecaabe74b7d86c38ab2ab44bd56cdcc33645a (diff) | |
| parent | 8df1c84e7272a5e24b563df7e50111dc81014d4a (diff) | |
Merge branch 'vxlan-vnifilter-fix-vni-add-update-notifications'
Andy Roulin says:
====================
vxlan: vnifilter: fix VNI add/update notifications
When a vxlan device has vnifilter enabled, userspace observers
(e.g., bridge monitor vni) miss VNI add events and see spurious
notifications on no-op VNI re-adds.
Patch 1 fixes the missing notification on VNI add: vxlan_vni_add()
guarded the notification on a 'changed' flag that vxlan_vni_update_group()
only sets when a multicast group or remote is supplied, so VNIs added
without a group (e.g., L3 VXLAN) were silently created.
Patch 2 fixes the spurious notification on VNI update: vxlan_vni_update()
tested 'if (changed)' against a bool pointer instead of dereferencing it,
so every re-add produced a notification regardless of whether anything
actually changed.
Patch 3 adds a selftest covering both bugs along with a few related
cases (add with remote, remote update, delete-nonexistent).
====================
Link: https://patch.msgid.link/20260602185138.253265-1-aroulin@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions
