From: Ilya Maximets <i.maximets@ovn.org>
To: Kyle Zeng <kylebot@openai.com>, netdev@vger.kernel.org
Cc: i.maximets@ovn.org, Aaron Conole <aconole@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>,
stable@vger.kernel.org, ovs dev <dev@openvswitch.org>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net] openvswitch: fix GSO userspace truncation underflow
Date: Wed, 8 Jul 2026 01:16:53 +0200 [thread overview]
Message-ID: <7bc054f8-7afc-4fa5-b392-bcad1f9d70bd@ovn.org> (raw)
In-Reply-To: <20260707221635.27489-1-kylebot@openai.com>
On 7/8/26 12:16 AM, Kyle Zeng wrote:
> OVS_ACTION_ATTR_TRUNC currently stores a delta from the original skb
> length in OVS_CB(skb)->cutlen. When a later userspace action segments a
> GSO skb, queue_gso_packets() reuses that delta for each smaller segment.
> A segment can then reach queue_userspace_packet() with cutlen greater
> than skb->len, underflowing the length passed to skb_zerocopy().
>
> Store the maximum preserved length instead and bound each consumer
> against the current skb length. Use U32_MAX as the no-truncation
> sentinel so the value remains valid if skb geometry changes before a
> consumer handles it.
>
> Fixes: f2a4d086ed4c ("openvswitch: Add packet truncation support.")
> Cc: stable@vger.kernel.org
> Assisted-by: Codex:gpt-5.5
> Signed-off-by: Kyle Zeng <kylebot@openai.com>
> ---
Thanks, Kyle! For the future, please, don't skip the general networking
maintainers and the ovs dev list while sending openvswitch -related patches.
Otherwise, this patch looks good to me:
Reviewed-by: Ilya Maximets <i.maximets@ovn.org>
prev parent reply other threads:[~2026-07-07 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 22:16 [PATCH net] openvswitch: fix GSO userspace truncation underflow Kyle Zeng
2026-07-07 23:16 ` Ilya Maximets [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=7bc054f8-7afc-4fa5-b392-bcad1f9d70bd@ovn.org \
--to=i.maximets@ovn.org \
--cc=aconole@redhat.com \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=kylebot@openai.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/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