Netdev List
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@nbd.name>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: [RFC] net: remove NETIF_F_GSO_FRAGLIST from NETIF_F_GSO_SOFTWARE
Date: Fri, 16 Aug 2024 17:29:21 +0200	[thread overview]
Message-ID: <2bb2f7ae-1175-4fff-ae4e-25c624295345@nbd.name> (raw)
In-Reply-To: <66bf5e76d36cf_1341d52942a@willemb.c.googlers.com.notmuch>

On 16.08.24 16:13, Willem de Bruijn wrote:
> Felix Fietkau wrote:
>> Several drivers set NETIF_F_GSO_SOFTWARE, but mangle fraglist GRO packets
>> in a way that they can't be properly segmented anymore.
> 
> Can you share a bit more concrete detail: which driver, for instance, and
> how does it mangle the packet?
> 
> I assume something with inserting or deleting tunnel headers. But the
> fraglist skbs should be able to reproduce the modified header in
> skb_segment_list?

I've received bug reports from a variety of people, often with very 
little context, usually crashing while segmenting fraglist skbs.

The ones that people were able to easily reproduce involved bridging 
with vxlan or virtio net devices. People using those two reported that 
my patch fixed their crashes.

I will try to gather more information about the root cause of the crashes.

- Felix

  reply	other threads:[~2024-08-16 15:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16  7:59 [RFC] net: remove NETIF_F_GSO_FRAGLIST from NETIF_F_GSO_SOFTWARE Felix Fietkau
2024-08-16 14:13 ` Willem de Bruijn
2024-08-16 15:29   ` Felix Fietkau [this message]
2024-08-20 13:12 ` Alexander Lobakin

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=2bb2f7ae-1175-4fff-ae4e-25c624295345@nbd.name \
    --to=nbd@nbd.name \
    --cc=netdev@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