From: Antoine Tenart <atenart@kernel.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: steffen.klassert@secunet.com, willemdebruijn.kernel@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net v3 3/4] udp: do not transition UDP GRO fraglist partial checksums to unnecessary
Date: Mon, 25 Mar 2024 11:37:15 +0100 [thread overview]
Message-ID: <171136303579.5526.5377651702776757800@kwain> (raw)
In-Reply-To: <65fdc00454e16_2bd0fb2948c@willemb.c.googlers.com.notmuch>
Quoting Willem de Bruijn (2024-03-22 18:29:40)
> Antoine Tenart wrote:
> > UDP GRO validates checksums and in udp4/6_gro_complete fraglist packets
> > are converted to CHECKSUM_UNNECESSARY to avoid later checks. However
> > this is an issue for CHECKSUM_PARTIAL packets as they can be looped in
> > an egress path and then their partial checksums are not fixed.
> >
> > Different issues can be observed, from invalid checksum on packets to
> > traces like:
> >
> > gen01: hw csum failure
> > skb len=3008 headroom=160 headlen=1376 tailroom=0
> > mac=(106,14) net=(120,40) trans=160
> > shinfo(txflags=0 nr_frags=0 gso(size=0 type=0 segs=0))
> > csum(0xffff232e ip_summed=2 complete_sw=0 valid=0 level=0)
> > hash(0x77e3d716 sw=1 l4=1) proto=0x86dd pkttype=0 iif=12
> > ...
> >
> > Fix this by only converting CHECKSUM_NONE packets to
> > CHECKSUM_UNNECESSARY by reusing __skb_incr_checksum_unnecessary.
> >
> > Fixes: 9fd1ff5d2ac7 ("udp: Support UDP fraglist GRO/GSO.")
> > Signed-off-by: Antoine Tenart <atenart@kernel.org>
>
> Should fraglist UDP GRO and non-fraglist (udp_gro_complete_segment)
> have the same checksumming behavior?
They can't as non-fraglist GRO packets can be aggregated, csum can't
just be converted there. It seems non-fraglist handles csum as it should
already, except for tunneled packets but that's why patch 4 prevents
those packets from being GROed.
> Second, this leaves CHECKSUM_COMPLETE as is. Is that intentional? I
> don't immediately see where GSO skb->csum would be updated.
That is intentional, fraglist GSO packets aren't modified and csums
don't need to be updated. The issues are with converting the checksum
type: partial checksum information can be lost.
Thanks,
Antoine
next prev parent reply other threads:[~2024-03-25 10:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 11:46 [PATCH net v3 0/4] gro: various fixes related to UDP tunnels Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 1/4] udp: do not accept non-tunnel GSO skbs landing in a tunnel Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 2/4] gro: fix ownership transfer Antoine Tenart
2024-03-22 11:46 ` [PATCH net v3 3/4] udp: do not transition UDP GRO fraglist partial checksums to unnecessary Antoine Tenart
2024-03-22 17:29 ` Willem de Bruijn
2024-03-25 10:37 ` Antoine Tenart [this message]
2024-03-25 18:39 ` Willem de Bruijn
2024-03-26 9:44 ` Antoine Tenart
2024-03-26 13:37 ` Willem de Bruijn
2024-03-22 11:46 ` [PATCH net v3 4/4] udp: prevent local UDP tunnel packets from being GROed Antoine Tenart
2024-03-22 22:55 ` [PATCH net v3 0/4] gro: various fixes related to UDP tunnels Jakub Kicinski
2024-03-25 10:16 ` Antoine Tenart
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=171136303579.5526.5377651702776757800@kwain \
--to=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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