All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Willem de Bruijn <willemb@google.com>
Cc: Christian Theune <christian@theune.cc>,
	regressions@lists.linux.dev, stable@vger.kernel.org,
	netdev@vger.kernel.org, mathieu.tortuyaux@gmail.com,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Subject: Re: Follow-up to "net: drop bad gso csum_start and offset in virtio_net_hdr" - backport for 5.15 needed
Date: Mon, 9 Sep 2024 19:03:28 +0200	[thread overview]
Message-ID: <2024090952-grope-carol-537b@gregkh> (raw)
In-Reply-To: <CA+FuTSdqnNq1sPMOUZAtH+zZy+Fx-z3pL-DUBcVbhc0DZmRWGQ@mail.gmail.com>

On Mon, Sep 09, 2024 at 12:05:17AM -0400, Willem de Bruijn wrote:
> On Tue, Sep 3, 2024 at 4:03 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Sep 03, 2024 at 09:37:30AM +0200, Christian Theune wrote:
> > > Hi,
> > >
> > > the issue was so far handled in https://lore.kernel.org/regressions/ZsyMzW-4ee_U8NoX@eldamar.lan/T/#m390d6ef7b733149949fb329ae1abffec5cefb99b and https://bugzilla.kernel.org/show_bug.cgi?id=219129
> > >
> > > I haven’t seen any communication whether a backport for 5.15 is already in progress, so I thought I’d follow up here.
> >
> > Someone needs to send a working set of patches to apply.
> 
> The following stack of patches applies cleanly to 5.15.166
> (original SHA1s, git log order, so inverse of order to apply):
> 
> 89add40066f9e net: drop bad gso csum_start and offset in virtio_net_hdr
> 9840036786d9 gso: fix dodgy bit handling for GSO_UDP_L4
> fc8b2a619469 net: more strict VIRTIO_NET_HDR_GSO_UDP_L4 validation
> 
> All three are already present in 6.1.109
> 
> Please let me know if I should send that stack using git send-email,
> or whether this is sufficient into to backport.

I just tried it, they do not apply cleanly here for me at all :(

> The third commit has one Fixes referencing them:
> 
> 1382e3b6a350 net: change maximum number of UDP segments to 128
> 
> This simple -2/+2 line patch unfortunately cannot be backported
> without conflicts without backporting non-stable feature changes.
> There is a backport to 6.1.y, but that also won't apply cleanly to
> 5.15.166 without backporting a feature (e2a4392b61f6 "udp: introduce
> udp->udp_flags"), which itself does not apply cleanly.
> 
> So simplest is probably to fix up this commit and send it using git
> send-email. I can do that as part of the stack with the above 3
> patches, or stand-alone if the above can be cherry-picked by SHA1.

Please send me a set of working, and tested, patches and we will be glad
to consider it.

thanks,

greg k-h

  reply	other threads:[~2024-09-09 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  7:37 Follow-up to "net: drop bad gso csum_start and offset in virtio_net_hdr" - backport for 5.15 needed Christian Theune
2024-09-03  8:02 ` Greg KH
2024-09-09  4:05   ` Willem de Bruijn
2024-09-09 17:03     ` Greg KH [this message]
2024-09-09 18:34       ` Willem de Bruijn
2024-09-09 18:38         ` Christian Theune
2024-09-09 20:32           ` Willem de Bruijn
2024-09-10  6:32             ` Christian Theune
2024-09-11  7:39               ` Christian Theune
2024-09-11  7:43                 ` Greg KH

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=2024090952-grope-carol-537b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=christian@theune.cc \
    --cc=mathieu.tortuyaux@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=willemb@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.