David Miller wrote: > From: Dan Smith <danms@xxxxxxxxxx> > Date: Fri, 23 Apr 2010 07:55:37 -0700 > >> This helper allows kernel routines to create a socket in a given netns, >> instead of forcing it to the initial or current one. >> >> I know this seems like it's violating the netns boundary. The intended >> use (as in the following patches) is specifically when talking to RTNETLINK >> in another netns for the purposes of creating or examining resources there. >> It is expected that this will be used for that sort of transient socket >> creation only. In other words: > > If you can create netlink sockets in a remote NS you can also make > changes there, and the whole point is to disallow changes. > > So maybe you won't be making changes, but others will think about > using this and doing so. > > At a high level, I think this is a really bad idea, so I won't be > applying this, sorry. What this is changed to be a socket option or ioctl or some other mechanism that allows one to move an existing unbound, unconnected socket to another namespace? This way, we do not modify the namespace directly, but still have ability to move sockets into it for required communication. In my mind moving a socket is someone similar to moving an interface to a namespace. You just moving a required resource. Thanks -vlad > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
