From: patchwork-bot+netdevbpf@kernel.org
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
stefanha@redhat.com, shuah@kernel.org, bobbyeshleman@meta.com,
mst@redhat.com, corbet@lwn.net, skhan@linuxfoundation.org,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
kuniyu@google.com, ncardwell@google.com,
daan.j.demeyer@gmail.com
Subject: Re: [PATCH net v3 0/3] vsock: add write-once semantics to child_ns_mode
Date: Thu, 26 Feb 2026 10:20:09 +0000 [thread overview]
Message-ID: <177210120979.1146836.15985214642756769564.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260223-vsock-ns-write-once-v3-0-c0cde6959923@meta.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 23 Feb 2026 14:38:31 -0800 you wrote:
> Two administrator processes may race when setting child_ns_mode: one
> sets it to "local" and creates a namespace, but another changes it to
> "global" in between. The first process ends up with a namespace in the
> wrong mode. Make child_ns_mode write-once so that a namespace manager
> can set it once, check the value, and be guaranteed it won't change
> before creating its namespaces. Writing a different value after the
> first write returns -EBUSY.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] selftests/vsock: change tests to respect write-once child ns mode
https://git.kernel.org/netdev/net/c/a382a34276cb
- [net,v3,2/3] vsock: lock down child_ns_mode as write-once
https://git.kernel.org/netdev/net/c/102eab95f025
- [net,v3,3/3] vsock: document write-once behavior of the child_ns_mode sysctl
https://git.kernel.org/netdev/net/c/b6302e057fdc
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-26 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 22:38 [PATCH net v3 0/3] vsock: add write-once semantics to child_ns_mode Bobby Eshleman
2026-02-23 22:38 ` [PATCH net v3 1/3] selftests/vsock: change tests to respect write-once child ns mode Bobby Eshleman
2026-02-23 22:38 ` [PATCH net v3 2/3] vsock: lock down child_ns_mode as write-once Bobby Eshleman
2026-02-24 0:24 ` Bobby Eshleman
2026-02-24 15:10 ` Stefano Garzarella
2026-02-24 15:10 ` Stefano Garzarella
2026-02-23 22:38 ` [PATCH net v3 3/3] vsock: document write-once behavior of the child_ns_mode sysctl Bobby Eshleman
2026-02-24 15:10 ` Stefano Garzarella
2026-02-26 10:20 ` 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=177210120979.1146836.15985214642756769564.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=corbet@lwn.net \
--cc=daan.j.demeyer@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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