j> So ... how does user space know what "other_netns" is? That's the point, userspace doesn't know about and can't use this interface. This is a way for the kernel to open a socket in another netns to talk to that netns' RTNETLINK. I realize in its current form it could be used for something more nefarious, but it would be kernel code doing it. j> Also note Eric's recent patches introduced another way of opening a j> socket in a different namespace - are you using those in the j> abstraction to find what netns is? No. The process doing the checkpoint already has pointers to the tasks and thus their netns pointers. Eric's interface is an abstraction to allow userspace to do something similar, I think that using it from the kernel would be rather messy. -- Dan Smith IBM Linux Technology Center email: danms@xxxxxxxxxx _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
