netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Antoine Tenart <atenart@kernel.org>,
	 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 v2 3/4] udp: do not transition UDP fraglist to unnecessary checksum
Date: Thu, 21 Mar 2024 14:13:35 -0400	[thread overview]
Message-ID: <65fc78cfe99a2_25798a29475@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <171104177952.222877.10664469615735463255@kwain>

Antoine Tenart wrote:
> Quoting Willem de Bruijn (2024-03-21 15:58:17)
> > Antoine Tenart wrote:
> > > 
> > > If I sum up our discussion CHECKSUM_NONE conversion is wanted,
> > > CHECKSUM_UNNECESSARY conversion is a no-op and CHECKSUM_PARTIAL
> > > conversion breaks things. What about we just convert CHECKSUM_NONE to
> > > CHECKSUM_UNNECESSARY?
> > 
> > CHECKSUM_NONE cannot be converted to CHECKSUM_UNNECESSARY in the
> > receive path. Unless it is known to have been locally generated,
> > this means that the packet has not been verified yet.
> 
> I'm not sure to follow, non-partial checksums are being verified by
> skb_gro_checksum_validate_zero_check in udp4/6_gro_receive before ending
> up in udp4/6_gro_complete. That's also probably what the original commit
> msg refers to: "After validating the csum, we mark ip_summed as
> CHECKSUM_UNNECESSARY for fraglist GRO packets".
> 
> With fraglist, the csum can then be converted to CHECKSUM_UNNECESSARY.

Oh yes, of course.

> Except for CHECKSUM_PARTIAL, as we discussed.

Because that is treated as equivalent to CHECKSUM_UNNECESSARY in the
ingress path, and if forwarded to an egress path, csum_start and
csum_off are set correctly. Also for all segs after segmentation.
Okay, that sounds fine then.

There are two cases here: csum_start points to the outer header or it
points to the inner header. I suppose that does not matter for
correctness post segmentation.

> Does that make sense? Anything we can do to help moving this forward?
> 
> Thanks!
> Antoine



  reply	other threads:[~2024-03-21 18:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19  9:31 [PATCH net v2 0/4] gro: various fixes related to UDP tunnels Antoine Tenart
2024-03-19  9:31 ` [PATCH net v2 1/4] udp: do not accept non-tunnel GSO skbs landing in a tunnel Antoine Tenart
2024-03-20  2:41   ` Jakub Kicinski
2024-03-20 11:11     ` Antoine Tenart
2024-03-20 10:34   ` Nikolay Aleksandrov
2024-03-20 11:13     ` Antoine Tenart
2024-03-19  9:31 ` [PATCH net v2 2/4] gro: fix ownership transfer Antoine Tenart
2024-03-19 13:13   ` Willem de Bruijn
2024-03-19  9:31 ` [PATCH net v2 3/4] udp: do not transition UDP fraglist to unnecessary checksum Antoine Tenart
2024-03-19 13:38   ` Willem de Bruijn
2024-03-19 16:01     ` Antoine Tenart
2024-03-20 13:00       ` Willem de Bruijn
2024-03-20 15:08         ` Antoine Tenart
2024-03-20 20:43           ` Willem de Bruijn
2024-03-21  8:48             ` Antoine Tenart
2024-03-21 12:42               ` Paolo Abeni
2024-03-21 14:58               ` Willem de Bruijn
2024-03-21 17:22                 ` Antoine Tenart
2024-03-21 18:13                   ` Willem de Bruijn [this message]
2024-03-22 10:48                     ` Antoine Tenart
2024-03-19  9:31 ` [PATCH net v2 4/4] udp: prevent local UDP tunnel packets from being GROed 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=65fc78cfe99a2_25798a29475@willemb.c.googlers.com.notmuch \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=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 \
    /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).