From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Heusel <christian@heusel.eu>
Cc: 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,
mst@redhat.com, netdev@vger.kernel.org, pabeni@redhat.com,
stable@vger.kernel.org, willemb@google.com
Subject: Re: [PATCH net] net: drop bad gso csum_start and offset in virtio_net_hdr
Date: Thu, 8 Aug 2024 08:38:28 +0200 [thread overview]
Message-ID: <2024080857-contusion-womb-aae1@gregkh> (raw)
In-Reply-To: <146d2c9f-f2c3-4891-ac48-a3e50c863530@heusel.eu>
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?
And how was this tested, it does not apply cleanly to the trees for me
at all.
confused,
greg k-h
next prev parent reply other threads:[~2024-08-08 6:38 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 [this message]
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
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=2024080857-contusion-womb-aae1@gregkh \
--to=gregkh@linuxfoundation.org \
--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=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).