From: Bobby Eshleman <bobbyeshleman@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Shuah Khan <shuah@kernel.org>
Cc: kvm@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
Bobby Eshleman <bobbyeshleman@gmail.com>,
Bobby Eshleman <bobbyeshleman@meta.com>
Subject: [PATCH RFC net-next v4 09/11] hv_sock: add netns hooks
Date: Mon, 16 Jun 2025 21:32:58 -0700 [thread overview]
Message-ID: <20250616-vsock-vmtest-v4-9-bdd1659c33fb@meta.com> (raw)
In-Reply-To: <20250616-vsock-vmtest-v4-0-bdd1659c33fb@meta.com>
From: Bobby Eshleman <bobbyeshleman@meta.com>
Make NS changes not break hyperv. Guest vsocks still remain in the
global namespace always, so the behavior is unchanged.
Signed-off-by: Bobby Eshleman <bobbyeshleman@meta.com>
---
net/vmw_vsock/hyperv_transport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/vmw_vsock/hyperv_transport.c b/net/vmw_vsock/hyperv_transport.c
index 31342ab502b4..85b22366ef00 100644
--- a/net/vmw_vsock/hyperv_transport.c
+++ b/net/vmw_vsock/hyperv_transport.c
@@ -313,7 +313,7 @@ static void hvs_open_connection(struct vmbus_channel *chan)
return;
hvs_addr_init(&addr, conn_from_host ? if_type : if_instance);
- sk = vsock_find_bound_socket(&addr);
+ sk = vsock_find_bound_socket(&addr, vsock_global_net());
if (!sk)
return;
--
2.47.1
next prev parent reply other threads:[~2025-06-17 4:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 4:32 [PATCH RFC net-next v4 00/11] vsock: add namespace support to vhost-vsock Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 01/11] selftests/vsock: add NS tests to vmtest.sh Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 02/11] vsock: a per-net vsock NS mode state Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 03/11] vsock: add vsock net ns helpers Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 04/11] vsock: add net to vsock skb cb Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 05/11] vsock: add common code for vsock NS support Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 06/11] virtio-vsock: add netns to common code Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 07/11] vhost/vsock: add netns support Bobby Eshleman
2025-06-17 4:32 ` [PATCH RFC net-next v4 08/11] vsock/virtio: add netns hooks Bobby Eshleman
2025-06-17 4:32 ` Bobby Eshleman [this message]
2025-06-17 4:32 ` [PATCH RFC net-next v4 10/11] vsock/vmci: " Bobby Eshleman
2025-06-17 4:33 ` [PATCH RFC net-next v4 11/11] vsock/loopback: add netns support Bobby Eshleman
2025-06-17 15:24 ` [PATCH RFC net-next v4 00/11] vsock: add namespace support to vhost-vsock Stefano Garzarella
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=20250616-vsock-vmtest-v4-9-bdd1659c33fb@meta.com \
--to=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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
all inboxes | Powered by JetHome®