On Wed, Feb 20, 2019 at 03:28:11PM -0500, Doug Ledford wrote: > Obviously, fixing the netlink would be the more robust solution. I think the way Parav has it works reasonably OK. The admin can toggle the switch *before* creating any net namespaces and it is perfectly atomic and non-disruptive. Trying to make it be a strong fence after net namespaces .. the best we could probably do is to run over the client list and call a new callback that should destroy anything outside the namespace. This would make particular sense if we also didn't do client init/uninit during NS change but just let each client fix its own stuff. Parav? Does any client other that uverbs need to do anything during NS change? Jason
