From: Ilya Maximets <i.maximets@ovn.org>
To: Norbert Szetei <norbert@doyensec.com>, netdev@vger.kernel.org
Cc: "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>,
Steffen Klassert <steffen.klassert@secunet.com>,
Kuan-Ting Chen <h3xrabbit@gmail.com>,
Zoltan Kiss <zoltan.kiss@citrix.com>,
dev@openvswitch.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/2] openvswitch: only skb_tx_error() a packet we are about to drop
Date: Thu, 13 Aug 2026 12:00:30 +0200 [thread overview]
Message-ID: <b20650c2-1adb-4902-b2b1-9bca91b95dec@ovn.org> (raw)
In-Reply-To: <C35992B1-7740-4886-94FF-F85DE8B0106F@doyensec.com>
On 8/13/26 7:47 AM, Norbert Szetei wrote:
> queue_userspace_packet() borrows the packet skb -- it only copies it into
> a private netlink message (user_skb) and does not own it; on return
> do_execute_actions() keeps forwarding it through the flow's remaining
> actions. Its error path nevertheless calls skb_tx_error(skb), which via
> skb_zcopy_clear() does skb_shinfo(skb)->flags &= ~SKBFL_ALL_ZEROCOPY,
> stripping SKBFL_SHARED_FRAG from that live skb (skb_tx_error()'s kerneldoc
> says "skb must be freed afterwards").
>
> For a MSG_ZEROCOPY skb carrying page-cache frags, SKBFL_SHARED_FRAG is
> what makes esp_input() skb_cow_data() before in-place AEAD; once it is
> stripped a later local ESP-in-UDP delivery decrypts in place over pages
> the sender does not own -- an unprivileged page-cache write (the
> "Fragnesia" primitive).
> do_execute_actions() ignores output_userspace()'s return value, so any
> action after a failed USERSPACE upcall inherits the stripped skb.
>
> Move the skb_tx_error() to the flow-miss drop path - the "default"
> branch of ovs_dp_process_packet()'s switch(error), before kfree_skb().
>
> The call has been here since commit 36d5fe6a0007 ("core, nfqueue,
> openvswitch: Orphan frags in skb_zerocopy and handle errors") but was
> harmless until esp_input() began relying on SKBFL_SHARED_FRAG to gate
> in-place decrypt; only then did stripping it on a still-forwarded skb
> become a page-cache write primitive.
>
> Fixes: 36d5fe6a0007 ("core, nfqueue, openvswitch: Orphan frags in skb_zerocopy and handle errors")
> Fixes: f4c50a4034e6 ("xfrm: esp: avoid in-place decrypt on shared skb frags")
> Cc: stable@vger.kernel.org
> Assisted-by: Claude:claude-opus-5
> Signed-off-by: Norbert Szetei <norbert@doyensec.com>
> ---
Reviewed-by: Ilya Maximets <i.maximets@ovn.org>
next prev parent reply other threads:[~2026-08-13 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 5:41 [PATCH net 0/2] net: don't strip zerocopy frag markers from a forwarded skb Norbert Szetei
2026-08-13 5:47 ` [PATCH net 1/2] openvswitch: only skb_tx_error() a packet we are about to drop Norbert Szetei
2026-08-13 5:49 ` [PATCH net 2/2] net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy() Norbert Szetei
2026-08-13 10:01 ` Ilya Maximets
2026-08-13 10:00 ` Ilya Maximets [this message]
2026-08-14 11:01 ` [PATCH net 1/2] openvswitch: only skb_tx_error() a packet we are about to drop Norbert Szetei
2026-08-14 12:31 ` Ilya Maximets
2026-08-14 13:40 ` Norbert Szetei
2026-08-14 14:52 ` Ilya Maximets
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=b20650c2-1adb-4902-b2b1-9bca91b95dec@ovn.org \
--to=i.maximets@ovn.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=h3xrabbit@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=norbert@doyensec.com \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=zoltan.kiss@citrix.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