Thread (7 messages) 7 messages, 4 authors, 2026-03-12

Re: [PATCH net-next v4] vsock: add G2H fallback for CIDs not owned by H2G transport

From: patchwork-bot+netdevbpf@kernel.org
Date: 2026-03-12 10:10:28
Also in: kvm, lkml, virtualization

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni [off-list ref]:

On Wed, 4 Mar 2026 23:00:27 +0000 you wrote:
When no H2G transport is loaded, vsock currently routes all CIDs to the
G2H transport (commit 65b422d9b61b ("vsock: forward all packets to the
host when no H2G is registered"). Extend that existing behavior: when
an H2G transport is loaded but does not claim a given CID, the
connection falls back to G2H in the same way.

This matters in environments like Nitro Enclaves, where an instance may
run nested VMs via vhost-vsock (H2G) while also needing to reach sibling
enclaves at higher CIDs through virtio-vsock-pci (G2H). With the old
code, any CID > 2 was unconditionally routed to H2G when vhost was
loaded, making those enclaves unreachable without setting
VMADDR_FLAG_TO_HOST explicitly on every connect.

[...]
Here is the summary with links:
  - [net-next,v4] vsock: add G2H fallback for CIDs not owned by H2G transport
    https://git.kernel.org/netdev/net-next/c/0de607dc4fd8

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help