From: Jongmin Jang <payload.jang@gmail.com>
To: Norbert Szetei <norbert@doyensec.com>
Cc: Jongmin Jang <payload.jang@gmail.com>,
netdev@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>,
Aaron Conole <aconole@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>,
Ilya Maximets <i.maximets@ovn.org>,
linux-kernel@vger.kernel.org, dev@openvswitch.org
Subject: Re: [PATCH net v2 3/3] net: skbuff: don't touch shared zerocopy state in skb_tx_error()
Date: Tue, 18 Aug 2026 03:30:09 +0900 [thread overview]
Message-ID: <20260817183009.357-2-payload.jang@gmail.com> (raw)
In-Reply-To: <F34B6E46-6B01-4106-A1DF-1BB9E29320BB@doyensec.com>
Hi Norbert,
I independently tested this patch as part of the v2 series using a
separate, non-destructive page-cache canary reproducer.
The test exercised the cloned OVS path while the original skb continued
through the remaining actions:
clone(userspace(pid=1)),2
Before the fix, the root-owned read-only page-cache canary changed. With
v2 applied, the canary remained unchanged. No kernel warning, oops, or
panic was observed.
Tested-by: Jongmin Jang <payload.jang@gmail.com>
Best regards,
Jongmin Jang
prev parent reply other threads:[~2026-08-17 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 6:48 [PATCH net v2 0/3] net: don't strip zerocopy frag markers from a forwarded skb Norbert Szetei
2026-08-16 6:51 ` [PATCH net v2 1/3] openvswitch: only skb_tx_error() a packet we are about to drop Norbert Szetei
2026-08-17 18:30 ` Jongmin Jang
2026-08-16 6:55 ` [PATCH net v2 2/3] net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy() Norbert Szetei
2026-08-16 6:57 ` [PATCH net v2 3/3] net: skbuff: don't touch shared zerocopy state in skb_tx_error() Norbert Szetei
2026-08-17 16:47 ` Ilya Maximets
2026-08-17 18:30 ` Jongmin Jang [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=20260817183009.357-2-payload.jang@gmail.com \
--to=payload.jang@gmail.com \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=norbert@doyensec.com \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).