Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Ian Kumlien <ian.kumlien@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [Intel-wired-lan] bug with rx-udp-gro-forwarding offloading?
Date: Tue, 27 Jun 2023 11:19:05 +0200	[thread overview]
Message-ID: <0a040331995c072c56fce58794848f5e9853c44f.camel@redhat.com> (raw)
In-Reply-To: <CAA85sZu=CzJx9QD87-vehOStzO9qHUSWk6DXZg3TzJeqOV5-aw@mail.gmail.com>

On Mon, 2023-06-26 at 20:59 +0200, Ian Kumlien wrote:
> On Mon, Jun 26, 2023 at 8:20 PM Ian Kumlien <ian.kumlien@gmail.com> wrote:
> > 
> > Nevermind, I think I found it, I will loop this thing until I have a
> > proper trace....
> 
> Still some question marks, but much better

Thanks!
> 
> cat bug.txt | ./scripts/decode_stacktrace.sh vmlinux
> [   62.624003] BUG: kernel NULL pointer dereference, address: 00000000000000c0
> [   62.631083] #PF: supervisor read access in kernel mode
> [   62.636312] #PF: error_code(0x0000) - not-present page
> [   62.641541] PGD 0 P4D 0
> [   62.644174] Oops: 0000 [#1] PREEMPT SMP NOPTI
> [   62.648629] CPU: 1 PID: 913 Comm: napi/eno2-79 Not tainted 6.4.0 #364
> [   62.655162] Hardware name: Supermicro Super Server/A2SDi-12C-HLN4F,
> BIOS 1.7a 10/13/2022
> [   62.663344] RIP: 0010:__udp_gso_segment
> (./include/linux/skbuff.h:2858 ./include/linux/udp.h:23
> net/ipv4/udp_offload.c:228 net/ipv4/udp_offload.c:261
> net/ipv4/udp_offload.c:277)

So it's faulting here:

static struct sk_buff *__udpv4_gso_segment_list_csum(struct sk_buff *segs)
{
        struct sk_buff *seg;
        struct udphdr *uh, *uh2;
        struct iphdr *iph, *iph2;

        seg = segs;
        uh = udp_hdr(seg);
        iph = ip_hdr(seg);

        if ((udp_hdr(seg)->dest == udp_hdr(seg->next)->dest) &&
        // ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The GSO segment has been assembled by skb_gro_receive_list()
I guess seg->next is NULL, which is somewhat unexpected as
napi_gro_complete() clears the gso_size when sending up the stack a
single frame.

On the flip side, AFAICS, nothing prevents the stack from changing the
aggregated packet layout (e.g. pulling data and/or linearizing the
skb).

In any case this looks more related to rx-gro-list then rx-udp-gro-
forwarding. I understand you have both feature enabled in your env?

Side questions: do you have any non trivial nf/br filter rule?

The following could possibly validate the above and avoid the issue,
but it's a bit papering over it. Could you please try it in your env?

Thanks!

Paolo
---
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
index 6c5915efbc17..75531686bfdf 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -4319,6 +4319,9 @@ struct sk_buff *skb_segment_list(struct sk_buff *skb,
 
 	skb->prev = tail;
 
+	if (WARN_ON_ONCE(!skb->next))
+		goto err_linearize;
+
 	if (skb_needs_linearize(skb, features) &&
 	    __skb_linearize(skb))
 		goto err_linearize;

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-06-27  9:19 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 20:03 [Intel-wired-lan] bug with rx-udp-gro-forwarding offloading? Ian Kumlien
2023-06-25 10:59 ` Ian Kumlien
2023-06-26 13:39   ` Ian Kumlien
2023-06-26 14:17   ` Alexander Lobakin
2023-06-26 14:25     ` Ian Kumlien
2023-06-26 16:42       ` Paolo Abeni
2023-06-26 17:07       ` Alexander Lobakin
2023-06-26 17:24         ` Ian Kumlien
2023-06-26 17:30           ` Ian Kumlien
2023-06-26 17:55             ` Paolo Abeni
2023-06-26 18:01               ` Ian Kumlien
2023-06-26 18:20                 ` Ian Kumlien
2023-06-26 18:59                   ` Ian Kumlien
2023-06-27  9:19                     ` Paolo Abeni [this message]
2023-06-27 12:31                       ` Ian Kumlien
2023-06-28  7:37                         ` Ian Kumlien
2023-06-28  9:06                           ` Paolo Abeni
2023-06-28 11:47                             ` Ian Kumlien
2023-06-28 12:04                               ` Ian Kumlien
2023-06-28 15:14                                 ` Paolo Abeni
2023-06-28 20:18                                   ` Ian Kumlien
2023-06-29 10:50                                     ` Ian Kumlien
2023-07-03  9:37                                       ` Ian Kumlien
2023-07-04 10:10                                         ` Paolo Abeni
2023-07-04 11:36                                           ` Ian Kumlien
2023-07-04 12:54                                             ` Paolo Abeni
2023-07-04 13:23                                               ` Ian Kumlien
2023-07-04 13:41                                                 ` Paolo Abeni
2023-07-04 14:06                                                   ` Ian Kumlien
2023-07-04 14:27                                                     ` Ian Kumlien
2023-07-04 14:57                                                       ` Ian Kumlien
2023-07-05 10:28                                                       ` Paolo Abeni
2023-07-05 11:32                                                         ` Ian Kumlien
2023-07-05 13:29                                                           ` Paolo Abeni
2023-07-05 13:58                                                             ` Ian Kumlien
2023-07-06  8:42                                                               ` Paolo Abeni
2023-07-06 11:27                                                                 ` Ian Kumlien
2023-07-06 13:01                                                                   ` Paolo Abeni
2023-07-06 13:56                                                                     ` Eric Dumazet
2023-07-06 14:04                                                                       ` Paolo Abeni
2023-07-06 16:17                                                                         ` Ian Kumlien
2023-07-06 17:10                                                                           ` Paolo Abeni
2023-07-06 17:43                                                                             ` Ian Kumlien
2023-07-06 22:32                                                                             ` Ian Kumlien
2023-07-06 22:41                                                                               ` Ian Kumlien
2023-07-07  6:55                                                                               ` Paolo Abeni

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=0a040331995c072c56fce58794848f5e9853c44f.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=edumazet@google.com \
    --cc=ian.kumlien@gmail.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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