From: Sasha Levin <sashal@kernel.org>
To: Brett A C Sheffield <bacs@librecast.net>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
Salvatore Bonaccorso <carnil@debian.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Oscar Maes <oscmaes92@gmail.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@kernel.org>
Subject: Re: [stable-6.16|lts-6.12] net: ipv4: fix regression in local-broadcast routes
Date: Wed, 3 Sep 2025 12:10:57 -0400 [thread overview]
Message-ID: <aLhokYGMkEGhQ85Y@laps> (raw)
In-Reply-To: <aLhVHLbqFCB6BoB2@karahi.gladserv.com>
On Wed, Sep 03, 2025 at 04:47:56PM +0200, Brett A C Sheffield wrote:
>On 2025-09-03 16:42, Sedat Dilek wrote:
>> On Fri, Aug 29, 2025 at 8:45 PM Salvatore Bonaccorso <carnil@debian.org> wrote:
>> >
>> > On Fri, Aug 29, 2025 at 06:56:52PM +0200, Sedat Dilek wrote:
>> > > Hi Sasha and Greg,
>> > >
>> > > Salvatore Bonaccorso <carnil@debian.org> from Debian Kernel Team
>> > > included this regression-fix already.
>> > >
>> > > Upstream commit 5189446ba995556eaa3755a6e875bc06675b88bd
>> > > "net: ipv4: fix regression in local-broadcast routes"
>> > >
>> > > As far as I have seen this should be included in stable-6.16 and
>> > > LTS-6.12 (for other stable branches I simply have no interest - please
>> > > double-check).
>> > >
>> > > I am sure Sasha's new kernel-patch-AI tool has catched this - just
>> > > kindly inform you.
>> >
>> > As 9e30ecf23b1b ("net: ipv4: fix incorrect MTU in broadcast routes")
>> > has been backported to all stable series in v5.4.297, v5.10.241,
>> > v5.15.190, v6.1.149, v6.6.103, v6.12.43, v6.15.11 and v6.16.2 the fix
>> > fixiing commit 5189446ba995 ("net: ipv4: fix regression in
>> > local-broadcast routes") would need to go as well to all of those
>> > series IMHO.
>> >
>>
>> Looks like next stable releases will include this bugfix - checked
>> stable-6.x only.
>
>Yes, the patch has been backported to all stable RCs.
Sorry, I forgot to reply - it was properly tagged for stable, so Greg would
have picked it up at some point, but I just did so manually to address the
regression.
--
Thanks,
Sasha
prev parent reply other threads:[~2025-09-03 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 16:56 [stable-6.16|lts-6.12] net: ipv4: fix regression in local-broadcast routes Sedat Dilek
2025-08-29 18:45 ` Salvatore Bonaccorso
2025-09-03 14:42 ` Sedat Dilek
2025-09-03 14:47 ` Brett A C Sheffield
2025-09-03 16:10 ` Sasha Levin [this message]
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=aLhokYGMkEGhQ85Y@laps \
--to=sashal@kernel.org \
--cc=bacs@librecast.net \
--cc=carnil@debian.org \
--cc=dsahern@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=oscmaes92@gmail.com \
--cc=pabeni@redhat.com \
--cc=sedat.dilek@gmail.com \
--cc=stable@vger.kernel.org \
/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