On Sat Sep 12, 2026 at 4:04 PM EDT, Jakub Kicinski wrote: > 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. > > Signed-off-by: Jakub Kicinski <[email protected]> > ---
Reviewed-by: Daniel Zahka <[email protected]>
