public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Graf <graf@amazon.com>
Cc: virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, kvm@vger.kernel.org, eperezma@redhat.com,
	jasowang@redhat.com, mst@redhat.com, sgarzare@redhat.com,
	stefanha@redhat.com, bcm-kernel-feedback-list@broadcom.com,
	arnd@arndb.de, gregkh@linuxfoundation.org, corbet@lwn.net,
	bryan-bt.tan@broadcom.com, vishnu.dasa@broadcom.com,
	nh-open-source@amazon.com, syzbot@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next v4] vsock: add G2H fallback for CIDs not owned by H2G transport
Date: Thu, 12 Mar 2026 10:10:24 +0000	[thread overview]
Message-ID: <177331022429.4031253.15687388113936443008.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260304230027.59857-1-graf@amazon.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

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



      parent reply	other threads:[~2026-03-12 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 23:00 [PATCH net-next v4] vsock: add G2H fallback for CIDs not owned by H2G transport Alexander Graf
2026-03-05  9:51 ` Stefano Garzarella
2026-03-10  9:30   ` Paolo Abeni
2026-03-10  9:18 ` [net-next,v4] " Paolo Abeni
2026-03-10  9:26   ` Paolo Abeni
2026-03-10 11:07     ` [net-next, v4] " Alexander Graf
2026-03-12 10:10 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177331022429.4031253.15687388113936443008.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bryan-bt.tan@broadcom.com \
    --cc=corbet@lwn.net \
    --cc=eperezma@redhat.com \
    --cc=graf@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nh-open-source@amazon.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=syzbot@syzkaller.appspotmail.com \
    --cc=virtualization@lists.linux.dev \
    --cc=vishnu.dasa@broadcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox