public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Brett Sheffield <brett@librecast.net>
Cc: Willem de Bruijn <willemb@google.com>,
	stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: 6.12.y longterm regression - IPv6 UDP packet fragmentation
Date: Wed, 2 Jul 2025 11:59:30 +0200	[thread overview]
Message-ID: <2025070216-duplex-ecologist-20ce@gregkh> (raw)
In-Reply-To: <aFfO8a7vS1jeBonh@karahi.gladserv.com>

On Sun, Jun 22, 2025 at 11:37:53AM +0200, Brett Sheffield wrote:
> On 2025-06-22 11:10, Greg KH wrote:
> > On Tue, Jun 17, 2025 at 02:25:02PM -0400, Willem de Bruijn wrote:
> > > FWIW, I did not originally intend for these changes to make it to stable.
> > > 
> > > The simplest short term solution is to revert this patch out of the
> > > stable trees. But long term that may give more conflicts as later
> > > patches need to be backported? Not sure what is wiser in such cases.
> > 
> > For now, I've applied the above 2 to the 6.12.y tree.  They do not apply
> > any older.  If I should drop the change from the older stable trees,
> > please let me know.
> 
> Thanks Greg.
> 
> For the older stable trees I agree with Willem that reverting the patch is the
> simplest fix.
> 
> As it stands UDP is broken in the older stable trees, so if this can make it
> into the next stable release that would be a good thing.

Ok, can someone send me reverts for the needed branches?

thanks,

greg k-h

  reply	other threads:[~2025-07-02  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 11:04 6.12.y longterm regression - IPv6 UDP packet fragmentation Brett Sheffield
2025-06-17 13:47 ` Greg KH
2025-06-17 17:29   ` Brett Sheffield
2025-06-17 18:25     ` Willem de Bruijn
2025-06-22  9:10       ` Greg KH
2025-06-22  9:37         ` Brett Sheffield
2025-07-02  9:59           ` Greg KH [this message]
2025-07-02 11:37             ` [PATCH 6.6.y] Revert "ipv6: save dontfrag in cork" Brett A C Sheffield
2025-07-03 18:34               ` Sasha Levin
2025-07-02 11:38             ` [PATCH 5.15.y] " Brett A C Sheffield
2025-07-03 18:34               ` Sasha Levin
2025-07-02 11:41             ` [PATCH 5.10.y] " Brett A C Sheffield
2025-07-03 18:34               ` Sasha Levin
2025-07-02 11:41             ` [PATCH 6.1.y] " Brett A C Sheffield
2025-07-03 18:35               ` Sasha Levin

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=2025070216-duplex-ecologist-20ce@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=brett@librecast.net \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=willemb@google.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