Re: [PATCH net-next v7 0/7] vsock: assign the guest vsock device to a network namespace

From: Bobby Eshleman

Date: Fri Nov 20 2026 - 13:08:43 EST


On Thu, Nov 19, 2026 at 01:53:03PM -0800, Jakub Kicinski wrote:
> On Thu, 19 Nov 2026 09:42:04 -0800 Bobby Eshleman wrote:
> > On Wed, Nov 18, 2026 at 06:28:46PM -0800, Jakub Kicinski wrote:
> > > On Tue, 17 Nov 2026 17:54:43 -0800 Bobby Eshleman wrote:
> > > > vsock network namespaces let a host put each VM in a namespace of its
> > > > own. A guest has no equivalent yet. It has a single G2H device that
> > > > cannot be assigned to a network namespace.
> > >
> > > PW says this did not apply at the time of posting, pls respin
> >
> > Ah I forgot to call out in the cover that this now depends on this fix in
> > net:
> >
> > https://lore.kernel.org/all/20261116-vsock-tap-net-v1-1-7e24f45adad3@xxxxxxxx/
>
> If there's a dependency the posting has to be an RFC
>
> > In that thread Paolo is also wondering if it is really an improvement
> > rather than a fix, which is a fair take, so unless there are objections
> > I'll just pull that patch into this series.
>
> No need to repost that patch, we can apply it to net-next as is.
> The blocker is lack of an ACK from the vsock maintainers from my PoV.
> Please just wait for the net[-next] patch to settle, don't repost this.
> Enough noise on the list.

Sounds good, I'll wait for that patch before the respin of this one.

@Stefano, IIRC you may be on PTO right now, but if not do you mind
giving a look at
https://lore.kernel.org/all/20261116-vsock-tap-net-v1-1-7e24f45adad3@xxxxxxxx/
?

Best,
Bobby