Re: [PATCH net-next 1/8] udp: fixup csum for GSO receive slow path

On Mon, 2021-03-22 at 09:18 -0400, Willem de Bruijn wrote:

On Sun, Mar 21, 2021 at 1:01 PM Paolo Abeni [off-list ref] wrote:

quoted

When looping back UDP GSO over UDP tunnel packets to an UDP socket,
the individual packet csum is currently set to CSUM_NONE. That causes
unexpected/wrong csum validation errors later in the UDP receive path.

We could possibly addressing the issue with some additional check and
csum mangling in the UDP tunnel code. Since the issue affects only
this UDP receive slow path, let's set a suitable csum status there.

Signed-off-by: Paolo Abeni <pabeni@redhat.com>
---
 include/net/udp.h | 18 ++++++++++++++++++
 net/ipv4/udp.c    | 10 ++++++++++
 net/ipv6/udp.c    |  5 +++++
 3 files changed, 33 insertions(+)

diff --git a/include/net/udp.h b/include/net/udp.h
index d4d064c592328..007683eb3e113 100644
--- a/include/net/udp.h
+++ b/include/net/udp.h

@@ -515,6 +515,24 @@ static inline struct sk_buff *udp_rcv_segment(struct sock *sk,
        return segs;
 }

+static inline void udp_post_segment_fix_csum(struct sk_buff *skb, int level)
+{
+       /* UDP-lite can't land here - no GRO */
+       WARN_ON_ONCE(UDP_SKB_CB(skb)->partial_cov);
+
+       /* GRO already validated the csum up to 'level', and we just
+        * consumed one header, update the skb accordingly
+        */
+       UDP_SKB_CB(skb)->cscov = skb->len;
+       if (level) {
+               skb->ip_summed = CHECKSUM_UNNECESSARY;
+               skb->csum_level = 0;
+       } else {
+               skb->ip_summed = CHECKSUM_NONE;
+               skb->csum_valid = 1;
+       }

why does this function also update these fields for non-tunneled
packets? the commit only describes an issue with tunneled packets.

quoted

+}
+
 #ifdef CONFIG_BPF_SYSCALL
 struct sk_psock;
 struct proto *udp_bpf_get_proto(struct sock *sk, struct sk_psock *psock);

diff --git a/net/ipv4/udp.c b/net/ipv4/udp.c
index 4a0478b17243a..ff54135c51ffa 100644
--- a/net/ipv4/udp.c
+++ b/net/ipv4/udp.c

@@ -2168,6 +2168,7 @@ static int udp_queue_rcv_one_skb(struct sock *sk, struct sk_buff *skb)
 static int udp_queue_rcv_skb(struct sock *sk, struct sk_buff *skb)
 {
        struct sk_buff *next, *segs;
+       int csum_level;
        int ret;

        if (likely(!udp_unexpected_gso(sk, skb)))

@@ -2175,9 +2176,18 @@ static int udp_queue_rcv_skb(struct sock *sk, struct sk_buff *skb)

        BUILD_BUG_ON(sizeof(struct udp_skb_cb) > SKB_GSO_CB_OFFSET);
        __skb_push(skb, -skb_mac_offset(skb));
+       csum_level = !!(skb_shinfo(skb)->gso_type &
+                       (SKB_GSO_UDP_TUNNEL | SKB_GSO_UDP_TUNNEL_CSUM));
        segs = udp_rcv_segment(sk, skb, true);
        skb_list_walk_safe(segs, skb, next) {
                __skb_pull(skb, skb_transport_offset(skb));
+
+               /* UDP GSO packets looped back after adding UDP encap land here with CHECKSUM none,
+                * instead of adding another check in the tunnel fastpath, we can force valid
+                * csums here (packets are locally generated).
+                * Additionally fixup the UDP CB
+                */
+               udp_post_segment_fix_csum(skb, csum_level);

How does this code differentiates locally generated packets with udp
tunnel headers from packets arriving from the wire, for which the
inner checksum may be incorrect?

First thing first, thank you for the detailed review. Digesting all the
comments will take time, so please excuse for some latency.

I'll try to reply to both your question here because the replies are
related.

My understanding is that UDP GRO, when processing UDP over UDP traffic
with the appropriate features bit set, will validate the checksum for
both the inner and the outer header - udp{4,6}_gro_receive will be
traversed twice, the fist one for the outer header, the 2nd for the
inner.

So when we reach here, the inner header csum could not be incorrect,
and I don't do anything to differentiate locally generated GSO packets
and GROed one to keep the code simpler.

The udp_post_segment_fix_csum() always set the csum info - even for non
tunneled packets to avoid additional branches/make the code more
complex. The csum should be valid in any scenario.

I guess I can mention the above either in a code comment and/or in the
commit message.

Cheers,

Paolo