summaryrefslogtreecommitdiff
path: root/tools/lib/python/kdoc/python_version.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-09-12 13:04:24 -0700
committerJakub Kicinski <kuba@kernel.org>2026-09-15 18:07:12 -0700
commitfb3ddbe2b5774f97a428bfb26711d68b966fcd0a (patch)
treedcffc6ea43d5e377aa16ad892d9fe19a3b5fa9f9 /tools/lib/python/kdoc/python_version.py
parent4d5d9f3a19682450858ff93ba3beaae65784ee3d (diff)
psp: notify about a disassociation once it has happened
The dev-change-ntf generated by dev-disassoc was built before the association was unlinked, so the assoc-list it carried still contained the device which was going away, and nothing corrected it afterwards. We don't really expect associations to change during a lifetime of a netns but this is still wrong. Netlink listeners need to be able to tell the current "state of the world" based on notifications. The notification had to be sent early because psp_nl_multicast_per_ns() derives the set of namespaces to notify from the association list, so a namespace losing its last associated device becomes unreachable once the entry is gone. In that case - get the netns from the netdev itself, and send that namespace a dev-del-ntf. If the netns had multiple associated netdevs and only one disassoc'd we'll still send a change notification, just with a correct list. Reviewed-by: Daniel Zahka <daniel.zahka@gmail.com> Link: https://patch.msgid.link/20260912200426.121025-5-kuba@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions