From: Felix Fietkau <nbd@nbd.name>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, stable@vger.kernel.org, maze@google.com,
shiming.cheng@mediatek.com, daniel@iogearbox.net,
lena.wang@mediatek.com, herbert@gondor.apana.org.au,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net] gso: fix gso fraglist segmentation after pull from frag_list
Date: Thu, 26 Sep 2024 11:17:34 +0200 [thread overview]
Message-ID: <daf225a9-8194-40c6-b797-8ab37de773a0@nbd.name> (raw)
In-Reply-To: <20240922150450.3873767-1-willemdebruijn.kernel@gmail.com>
On 22.09.24 17:03, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> Detect gso fraglist skbs with corrupted geometry (see below) and
> pass these to skb_segment instead of skb_segment_list, as the first
> can segment them correctly.
>
> Valid SKB_GSO_FRAGLIST skbs
> - consist of two or more segments
> - the head_skb holds the protocol headers plus first gso_size
> - one or more frag_list skbs hold exactly one segment
> - all but the last must be gso_size
>
> Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can
> modify these skbs, breaking these invariants.
>
> In extreme cases they pull all data into skb linear. For UDP, this
> causes a NULL ptr deref in __udpv4_gso_segment_list_csum at
> udp_hdr(seg->next)->dest.
>
> Detect invalid geometry due to pull, by checking head_skb size.
> Don't just drop, as this may blackhole a destination. Convert to be
> able to pass to regular skb_segment.
>
> Link: https://lore.kernel.org/netdev/20240428142913.18666-1-shiming.cheng@mediatek.com/
> Fixes: 3a1296a38d0c ("net: Support GRO/GSO fraglist chaining.")
> Signed-off-by: Willem de Bruijn <willemb@google.com>
> Cc: stable@vger.kernel.org
Reviewed-by: Felix Fietkau <nbd@nbd.name>
next prev parent reply other threads:[~2024-09-26 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 15:03 [PATCH net] gso: fix gso fraglist segmentation after pull from frag_list Willem de Bruijn
2024-09-24 17:47 ` Felix Fietkau
2024-09-24 19:50 ` Willem de Bruijn
2024-09-25 8:10 ` Felix Fietkau
2024-09-25 19:09 ` Willem de Bruijn
2024-09-25 20:59 ` Felix Fietkau
2024-09-25 21:12 ` Felix Fietkau
2024-09-26 7:19 ` Willem de Bruijn
2024-09-26 7:38 ` Felix Fietkau
2024-09-26 7:45 ` Willem de Bruijn
2024-09-26 7:16 ` Willem de Bruijn
2024-09-26 9:17 ` Felix Fietkau [this message]
2024-09-26 9:22 ` Willem de Bruijn
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=daf225a9-8194-40c6-b797-8ab37de773a0@nbd.name \
--to=nbd@nbd.name \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=lena.wang@mediatek.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shiming.cheng@mediatek.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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