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). Andy Roulin (3): vxlan: vnifilter: send notification on VNI add vxlan: vnifilter: fix spurious notification on VNI update selftests: net: add vxlan vnifilter notification test drivers/net/vxlan/vxlan_vnifilter.c | 5 +- tools/testing/selftests/net/Makefile | 1 + .../net/test_vxlan_vnifilter_notify.sh | 175 ++++++++++++++++++ 3 files changed, 178 insertions(+), 3 deletions(-) create mode 100755 tools/testing/selftests/net/test_vxlan_vnifilter_notify.sh -- 2.43.0
