From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, edumazet@google.com,
linux-kernel@vger.kernel.org, bobbyeshleman@meta.com,
kuba@kernel.org, virtualization@lists.linux.dev,
pabeni@redhat.com, mst@redhat.com, horms@kernel.org,
davem@davemloft.net
Subject: Re: [PATCH net 0/2] vsock: fix child netns mode initialization and restriction
Date: Fri, 13 Feb 2026 20:40:09 +0000 [thread overview]
Message-ID: <177101520983.2551386.9528402801702490594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260212205916.97533-1-sgarzare@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 12 Feb 2026 21:59:14 +0100 you wrote:
> This series fixes two issues in the vsock network namespace support
> recently introduced by commit eafb64f40ca4 ("vsock: add netns to vsock
> core").
>
> Patch 1 fixes `child_ns_mode` being always hardcoded to "global" for new
> namespaces, breaking propagation of the "local" mode through nested
> namespaces.
>
> [...]
Here is the summary with links:
- [net,1/2] vsock: fix child netns mode initialization
https://git.kernel.org/netdev/net/c/9dd391493a72
- [net,2/2] vsock: prevent child netns mode switch from local to global
https://git.kernel.org/netdev/net/c/6a997f38bdf8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-02-13 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 20:59 [PATCH net 0/2] vsock: fix child netns mode initialization and restriction Stefano Garzarella
2026-02-12 20:59 ` [PATCH net 1/2] vsock: fix child netns mode initialization Stefano Garzarella
2026-02-13 1:14 ` Bobby Eshleman
2026-02-12 20:59 ` [PATCH net 2/2] vsock: prevent child netns mode switch from local to global Stefano Garzarella
2026-02-13 1:19 ` Bobby Eshleman
2026-02-13 20:40 ` 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=177101520983.2551386.9528402801702490594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@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