From: Jakub Sitnicki <jakub@cloudflare.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, kernel-team@cloudflare.com,
Ivan Babrou <ivan@cloudflare.com>,
stable@vger.kernel.org
Subject: Re: [PATCH net] udp: Compute L4 checksum as usual when not segmenting the skb
Date: Thu, 10 Oct 2024 16:00:28 +0200 [thread overview]
Message-ID: <87ttdkxdkz.fsf@cloudflare.com> (raw)
In-Reply-To: <6707d74780461_2029212946a@willemb.c.googlers.com.notmuch> (Willem de Bruijn's message of "Thu, 10 Oct 2024 09:31:51 -0400")
On Thu, Oct 10, 2024 at 09:31 AM -04, Willem de Bruijn wrote:
> Jakub Sitnicki wrote:
>> If:
>>
>> 1) the user requested USO, but
>> 2) there is not enough payload for GSO to kick in, and
>> 3) the egress device doesn't offer checksum offload, then
>>
>> we want to compute the L4 checksum in software early on.
>>
>> In the case when we taking the GSO path, but it has been requested, the
>
> What does it refers to here?
That's a typo there. Will fix. It should have said:
In the case when we *not* taking the GSO path, but it has been
requested, ...
Pseudo code-wise something like:
s.setsockopt(SOL_UDP, UDP_SEGMENT, 1200)
s.sendto(b"x", ("192.0.2.1", 9))
>> software checksum fallback in skb_segment doesn't get a chance to compute
>> the full checksum, if the egress device can't do it. As a result we end up
>> sending UDP datagrams with only a partial checksum filled in, which the
>> peer will discard.
>>
>> Fixes: 10154dbded6d ("udp: Allow GSO transmit from devices with no checksum offload")
>> Reported-by: Ivan Babrou <ivan@cloudflare.com>
>> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
>> Cc: stable@vger.kernel.org
>> ---
>> This shouldn't have fallen through the cracks. I clearly need to extend the
>> net/udpgso selftests further to cover the whole TX path for software
>> USO+csum case. I will follow up with that but I wanted to get the fix out
>> in the meantime. Apologies for the oversight.
>> ---
>> net/ipv4/udp.c | 4 +++-
>> net/ipv6/udp.c | 4 +++-
>> 2 files changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/ipv4/udp.c b/net/ipv4/udp.c
>> index 8accbf4cb295..2849b273b131 100644
>> --- a/net/ipv4/udp.c
>> +++ b/net/ipv4/udp.c
>> @@ -951,8 +951,10 @@ static int udp_send_skb(struct sk_buff *skb, struct flowi4 *fl4,
>> skb_shinfo(skb)->gso_type = SKB_GSO_UDP_L4;
>> skb_shinfo(skb)->gso_segs = DIV_ROUND_UP(datalen,
>> cork->gso_size);
>> +
>> + /* Don't checksum the payload, skb will get segmented */
>> + goto csum_partial;
>> }
>> - goto csum_partial;
>
> The issue here is that GSO packets with CHECKSUM_NONE will get fixed
> software checksummed in skb_segment, but no such fallback path is
> entered for regular packets, right?
>
> We could setup CHECKSUM_PARTIAL and rely on validate_xmit_skb. But
> might as well do the software checksumming right here, as your
> patch does.
Yes, all correct.
To add to it - I figured that marking the skb with CHECKSUM_PARTIAL,
when device doesn't offer csum offload, would be more confusing.
>
> If I follow this all, ACK from me. Just want to make sure.
Thanks. I will carry it in v2.
Will wait a bit before respinning it.
Maybe Ivan can get a chance to this patch.
>> }
>>
>> if (is_udplite) /* UDP-Lite */
>> diff --git a/net/ipv6/udp.c b/net/ipv6/udp.c
>> index 52dfbb2ff1a8..0cef8ae5d1ea 100644
>> --- a/net/ipv6/udp.c
>> +++ b/net/ipv6/udp.c
>> @@ -1266,8 +1266,10 @@ static int udp_v6_send_skb(struct sk_buff *skb, struct flowi6 *fl6,
>> skb_shinfo(skb)->gso_type = SKB_GSO_UDP_L4;
>> skb_shinfo(skb)->gso_segs = DIV_ROUND_UP(datalen,
>> cork->gso_size);
>> +
>> + /* Don't checksum the payload, skb will get segmented */
>> + goto csum_partial;
>> }
>> - goto csum_partial;
>> }
>>
>> if (is_udplite)
>>
prev parent reply other threads:[~2024-10-10 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 12:14 [PATCH net] udp: Compute L4 checksum as usual when not segmenting the skb Jakub Sitnicki
2024-10-10 13:31 ` Willem de Bruijn
2024-10-10 14:00 ` Jakub Sitnicki [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=87ttdkxdkz.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=ivan@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--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