From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christian Heusel <christian@heusel.eu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
avladu@cloudbasesolutions.com, willemdebruijn.kernel@gmail.com,
alexander.duyck@gmail.com, arefev@swemel.ru, davem@davemloft.net,
edumazet@google.com, jasowang@redhat.com, kuba@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
stable@vger.kernel.org, willemb@google.com,
regressions@lists.linux.dev
Subject: Re: [PATCH net] net: drop bad gso csum_start and offset in virtio_net_hdr
Date: Wed, 14 Aug 2024 05:54:58 -0400 [thread overview]
Message-ID: <20240814055408-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <0d897b58-f4b8-4814-b3f9-5dce0540c81d@heusel.eu>
On Wed, Aug 14, 2024 at 11:46:30AM +0200, Christian Heusel wrote:
> On 24/08/08 11:52AM, Christian Heusel wrote:
> > On 24/08/08 08:38AM, Greg KH wrote:
> > > On Wed, Aug 07, 2024 at 08:34:48PM +0200, Christian Heusel wrote:
> > > > On 24/08/07 04:12PM, Greg KH wrote:
> > > > > On Mon, Aug 05, 2024 at 09:28:29PM +0000, avladu@cloudbasesolutions.com wrote:
> > > > > > Hello,
> > > > > >
> > > > > > This patch needs to be backported to the stable 6.1.x and 6.64.x branches, as the initial patch https://github.com/torvalds/linux/commit/e269d79c7d35aa3808b1f3c1737d63dab504ddc8 was backported a few days ago: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/include/linux/virtio_net.h?h=3Dv6.1.103&id=3D5b1997487a3f3373b0f580c8a20b56c1b64b0775
> > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/include/linux/virtio_net.h?h=3Dv6.6.44&id=3D90d41ebe0cd4635f6410471efc1dd71b33e894cf
> > > > >
> > > > > Please provide a working backport, the change does not properly
> > > > > cherry-pick.
> > > > >
> > > > > greg k-h
> > > >
> > > > Hey Greg, hey Sasha,
> > > >
> > > > this patch also needs backporting to the 6.6.y and 6.10.y series as the
> > > > buggy commit was backported to to all three series.
> > >
> > > What buggy commit?
> >
> > The issue is that commit e269d79c7d35 ("net: missing check virtio")
> > introduces a bug which is fixed by 89add40066f9 ("net: drop bad gso
> > csum_start and offset in virtio_net_hdr") which it also carries a
> > "Fixes:" tag for.
> >
> > Therefore it would be good to also get 89add40066f9 backported.
> >
> > > And how was this tested, it does not apply cleanly to the trees for me
> > > at all.
> >
> > I have tested this with the procedure as described in [0]:
> >
> > $ git switch linux-6.10.y
> > $ git cherry-pick -x 89add40066f9ed9abe5f7f886fe5789ff7e0c50e
> > Auto-merging net/ipv4/udp_offload.c
> > [linux-6.10.y fbc0d2bea065] net: drop bad gso csum_start and offset in virtio_net_hdr
> > Author: Willem de Bruijn <willemb@google.com>
> > Date: Mon Jul 29 16:10:12 2024 -0400
> > 3 files changed, 12 insertions(+), 11 deletions(-)
> >
> > This also works for linux-6.6.y, but not for linux-6.1.y, as it fails
> > with a merge error there.
> >
> > The relevant commit is confirmed to fix the issue in the relevant Githu
> > issue here[1]:
> >
> > @marek22k commented
> > > They both fix the problem for me.
> >
> > > confused,
> >
> > Sorry for the confusion! I hope the above clears things up a little :)
> >
> > > greg k-h
> >
> > Cheers,
> > Christian
> >
> > [0]: https://lore.kernel.org/all/2024060624-platinum-ladies-9214@gregkh/
> > [1]: https://github.com/tailscale/tailscale/issues/13041#issuecomment-2272326491
>
> Since I didn't hear from anybody so far about the above issue it's a bit
> unclear on how to proceed here. I still think that I would make sense to
> go with my above suggestion about patching at least 2 out of the 3
> stable series where the patch applies cleanly.
>
> ~ Chris
Do what Greg said:
Please provide a working backport, the change does not properly
cherry-pick.
that means, post backported patches to stable, copy list.
--
MST
next prev parent reply other threads:[~2024-08-14 9:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 2:32 [PATCH net] net: drop bad gso csum_start and offset in virtio_net_hdr Willem de Bruijn
2024-07-26 7:00 ` Eric Dumazet
2024-07-26 13:49 ` Willem de Bruijn
2024-07-26 8:23 ` Paolo Abeni
2024-07-26 13:52 ` Willem de Bruijn
2024-07-26 14:48 ` Paolo Abeni
2024-08-05 21:28 ` avladu
2024-08-07 14:12 ` Greg KH
2024-08-07 14:42 ` Adrian Vladu
2024-08-07 18:34 ` Christian Heusel
2024-08-08 6:38 ` Greg KH
2024-08-08 9:52 ` Christian Heusel
2024-08-08 9:57 ` Adrian Vladu
2024-08-14 9:46 ` Christian Heusel
2024-08-14 9:54 ` Michael S. Tsirkin [this message]
2024-08-14 10:05 ` Christian Heusel
2024-08-14 10:10 ` Adrian Vladu
2024-08-14 10:24 ` Christian Heusel
2024-08-14 13:53 ` Willem de Bruijn
2024-08-21 12:57 ` Vitaly Chikunov
2024-08-21 14:05 ` Willem de Bruijn
2024-08-26 14:10 ` Salvatore Bonaccorso
2024-08-26 20:07 ` Salvatore Bonaccorso
2024-08-27 13:16 ` Greg KH
2024-08-27 17:59 ` Vitaly Chikunov
2024-08-27 13:15 ` 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=20240814055408-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=arefev@swemel.ru \
--cc=avladu@cloudbasesolutions.com \
--cc=christian@heusel.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).