netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: "Vitaly Chikunov" <vt@altlinux.org>,
	"Christian Heusel" <christian@heusel.eu>,
	"Adrian Vladu" <avladu@cloudbasesolutions.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Greg KH" <gregkh@linuxfoundation.org>,
	"alexander.duyck@gmail.com" <alexander.duyck@gmail.com>,
	"arefev@swemel.ru" <arefev@swemel.ru>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"willemb@google.com" <willemb@google.com>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"David Prévot" <taffit@debian.org>
Subject: Re: [PATCH net] net: drop bad gso csum_start and offset in virtio_net_hdr
Date: Mon, 26 Aug 2024 16:10:21 +0200	[thread overview]
Message-ID: <ZsyMzW-4ee_U8NoX@eldamar.lan> (raw)
In-Reply-To: <66c5f41884850_da1e7294d2@willemb.c.googlers.com.notmuch>

Hi,

On Wed, Aug 21, 2024 at 10:05:12AM -0400, Willem de Bruijn wrote:
> Vitaly Chikunov wrote:
> > Willem,
> > 
> > On Wed, Aug 14, 2024 at 09:53:58AM GMT, Willem de Bruijn wrote:
> > > Christian Heusel wrote:
> > > > On 24/08/14 10:10AM, Adrian Vladu wrote:
> > > > > Hello,
> > > > > 
> > > > > The 6.6.y branch has the patch already in the stable queue -> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=3e713b73c01fac163a5c8cb0953d1e300407a773, and it should be available in the 6.6.46 upcoming minor.
> > > > > 
> > > > > Thanks, Adrian.
> > > > 
> > > > Yeah it's also queued up for 6.10, which I both missed (sorry for that!).
> > > > If I'm able to properly backport the patch for 6.1 I'll send that one,
> > > > but my hopes are not too high that this will work ..
> > > 
> > > There are two conflicts.
> > > 
> > > The one in include/linux/virtio_net.h is resolved by first backporting
> > > commit fc8b2a6194693 ("net: more strict VIRTIO_NET_HDR_GSO_UDP_L4
> > > validation")
> > > 
> > > We did not backport that to stable because there was some slight risk
> > > that applications might be affected. This has not surfaced.
> > > 
> > > The conflict in net/ipv4/udp_offload.c is not so easy to address.
> > > There were lots of patches between v6.1 and linus/master, with far
> > > fewer of these betwee v6.1 and linux-stable/linux-6.1.y.
> > 
> > BTW, we successfully cherry-picked 3 suggested[1] commits over v6.1.105 in
> > ALT, and there is no reported problems as of yet.
> > 
> >   89add40066f9 ("net: drop bad gso csum_start and offset in virtio_net_hdr")
> >   fc8b2a619469 ("net: more strict VIRTIO_NET_HDR_GSO_UDP_L4 validation")
> >   9840036786d9 ("gso: fix dodgy bit handling for GSO_UDP_L4")
> > 
> > [1] https://lore.kernel.org/all/2024081147-altitude-luminous-19d1@gregkh/
> 
> That's good to hear.
> 
> These are all fine to go to 6.1 stable.

FWIW, as we are hit by this issue for Debian bookworm, we have testing
as well from David Prévot <taffit@debian.org>, cf. the report in
https://bugs.debian.org/1079684 .

He mentions that the 9840036786d9 ("gso: fix dodgy bit handling for
GSO_UDP_L4") patch does not apply cleanly, looks to be because of
1fd54773c267 ("udp: allow header check for dodgy GSO_UDP_L4 packets.")
from 6.2-rc1, which are reverted in the commit.

Regards,
Salvatore

  reply	other threads:[~2024-08-26 14:10 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
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 [this message]
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=ZsyMzW-4ee_U8NoX@eldamar.lan \
    --to=carnil@debian.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=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=taffit@debian.org \
    --cc=vt@altlinux.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).