On Tue, Jan 13, 2026 at 02:45:32AM -0500, Michael S. Tsirkin wrote: > On Mon, Jan 12, 2026 at 07:11:10PM -0800, Bobby Eshleman wrote: > > From: Bobby Eshleman <[email protected]> > > > > Add netns logic to vsock core. Additionally, modify transport hook > > prototypes to be used by later transport-specific patches (e.g., > > *_seqpacket_allow()). > > > > Namespaces are supported primarily by changing socket lookup functions > > (e.g., vsock_find_connected_socket()) to take into account the socket > > namespace and the namespace mode before considering a candidate socket a > > "match". > > > > This patch also introduces the sysctl /proc/sys/net/vsock/ns_mode to > > report the mode and /proc/sys/net/vsock/child_ns_mode to set the mode > > for new namespaces. > > > > Add netns functionality (initialization, passing to transports, procfs, > > etc...) to the af_vsock socket layer. Later patches that add netns > > support to transports depend on this patch. > > > > dgram_allow(), stream_allow(), and seqpacket_allow() callbacks are > > modified to take a vsk in order to perform logic on namespace modes. In > > future patches, the net will also be used for socket > > lookups in these functions. > > > > Signed-off-by: Bobby Eshleman <[email protected]> > > --- > > Changes in v14: > > - include linux/sysctl.h in af_vsock.c > > - squash patch 'vsock: add per-net vsock NS mode state' into this patch > > (prior version can be found here): > > > > https://lore.kernel.org/all/[email protected]/) > > So, about the static port, are you going to address it in > the next version then?
Yes, just wanted to get the rebase out to unblock review of the child_ns_mode changes. I should have mentioned the static port was a known issue and still under discussion. - Bobby
