From: Jakub Kicinski <kuba@kernel.org>
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Bobby Eshleman <bobbyeshleman@meta.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Daan De Meyer <daan.j.demeyer@gmail.com>
Subject: Re: [PATCH net] vsock: lock down child_ns_mode as write-once
Date: Wed, 18 Feb 2026 16:41:19 -0800 [thread overview]
Message-ID: <20260218164119.72368d53@kernel.org> (raw)
In-Reply-To: <aZXlqv5ukWymz/NI@devvm11784.nha0.facebook.com>
On Wed, 18 Feb 2026 08:15:38 -0800 Bobby Eshleman wrote:
> > > I'm not sure what the policy is in netdev, but I would prefer to have
> > > selftest changes in another patch (I think earlier in the series so as
> > > not to break the bisection), in order to simplify backporting (e.g. in
> > > CentOS Stream, to keep the backport small, I didn't backport the dozens
> > > of patches for selftest that we did previously).
>
> Sounds good! I wasn't sure if breakage so tightly coupled should be in
> the same patch or not, I'm happy to split it up to ease backporting.
FWIW the netdev recommendation is indeed to split the selftests out.
Also to bungle selftest patches with the fix into one series targeting
net, even tho the selftests patches won't have a Fixes tag.
next prev parent reply other threads:[~2026-02-19 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 1:45 [PATCH net] vsock: lock down child_ns_mode as write-once Bobby Eshleman
2026-02-18 10:02 ` Stefano Garzarella
2026-02-18 10:43 ` Stefano Garzarella
2026-02-18 16:15 ` Bobby Eshleman
2026-02-19 0:41 ` Jakub Kicinski [this message]
2026-02-19 16:21 ` Bobby Eshleman
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=20260218164119.72368d53@kernel.org \
--to=kuba@kernel.org \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=daan.j.demeyer@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mst@redhat.com \
--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