From: Paolo Abeni <pabeni@redhat.com>
To: Ian Kumlien <ian.kumlien@gmail.com>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] bug with rx-udp-gro-forwarding offloading?
Date: Tue, 04 Jul 2023 15:41:19 +0200 [thread overview]
Message-ID: <062061fc4d4d3476e3b0255803b726956686eb19.camel@redhat.com> (raw)
In-Reply-To: <CAA85sZuQh0FMoGDFVyOad6G1UB9keodd3OCZ4d4r+xgXDArcVA@mail.gmail.com>
On Tue, 2023-07-04 at 15:23 +0200, Ian Kumlien wrote:
> On Tue, Jul 4, 2023 at 2:54 PM Paolo Abeni <pabeni@redhat.com> wrote:
> >
> > On Tue, 2023-07-04 at 13:36 +0200, Ian Kumlien wrote:
> > > Propper bug this time:
> > > cat bug.txt | ./scripts/decode_stacktrace.sh vmlinux
> >
> > To be sure, is this with the last patch I shared? this one I mean:
>
> The current modifications I have, on top of v6.4.1, is:
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index cea28d30abb5..8552caa197f9 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -4272,6 +4272,11 @@ struct sk_buff *skb_segment_list(struct sk_buff *skb,
>
> skb_shinfo(skb)->frag_list = NULL;
>
> + /* later code will clear the gso area in the shared info */
> + err = skb_header_unclone(skb, GFP_ATOMIC);
> + if (err)
> + goto err_linearize;
> +
> while (list_skb) {
> nskb = list_skb;
> list_skb = list_skb->next;
> @@ -4328,6 +4333,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;
> ---
>
> > https://lore.kernel.org/netdev/92a4d42491a2c219192ae86fa04b579ea3676d8c.camel@redhat.com/
> >
> > Could you please additionally enable CONFIG_DEBUG_NET in your build?
>
> Sure, will do
>
> > Could you please give a detailed description of your network topology
> > and the running traffic?
>
> This machine has two "real interfaces" and two interfaces that runs as
> bridges for virtual machines
> eno1 - real internal
> eno2 - bridge - internal
> eno3 - real external
> eno4 - bridge - external
>
> The bridges are used by three virtual machines, two of which are
> attached on both networks
>
> Traffic seemed to be video streaming, at least at first, now I don't
> really know. I do have a few smart devices so I assume there is
> a bit of multicast traffic as well - but not really anything unusual as such.
In there any XDP program running on the host side? Possibly changing
the packet hdr?
Thanks!
/P
next prev parent reply other threads:[~2023-07-04 13:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA85sZukiFq4A+b9+en_G85eVDNXMQsnGc4o-4NZ9SfWKqaULA@mail.gmail.com>
[not found] ` <CAA85sZvm1dL3oGO85k4R+TaqBiJsggUTpZmGpH1+dqdC+U_s1w@mail.gmail.com>
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
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 [this message]
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 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=062061fc4d4d3476e3b0255803b726956686eb19.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=aleksander.lobakin@intel.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
all inboxes | Powered by JetHome®