From: Greg KH <greg@kroah.com>
To: Florian Westphal <fw@strlen.de>
Cc: stable@vger.kernel.org, pablo@netfilter.org, linux@slavino.sk
Subject: Re: stable request: eaaff9b6702e ("netfilter: fib: avoid lookup if socket is available")
Date: Mon, 28 Apr 2025 13:50:01 +0200 [thread overview]
Message-ID: <2025042856-skimming-storm-a49b@gregkh> (raw)
In-Reply-To: <20250424183306.GA24548@breakpoint.cc>
On Thu, Apr 24, 2025 at 08:33:06PM +0200, Florian Westphal wrote:
> Hi Greg, hi Sasha,
>
> Could you please queue up
>
> eaaff9b6702e ("netfilter: fib: avoid lookup if socket is available")
>
> for 6.14 and 6.12?
>
> Unfortunately I did not realize that the missing handling of
> 'input' is not just a missing optimization but an actual bug fix, else
> I would have split this patch in two.
>
> The bug exists since 5.19, but its not a regression ('never worked').
>
> Given noone noticed/reported this until this week
> (https://lore.kernel.org/netfilter/20250422114352.GA2092@breakpoint.cc/),
> we think it makes sense to only apply this to the two most recent trees
> and keep the rest as-is, users of those trees evidently don't use the
> b0rken configuration or they would have complained long ago.
>
> The commit cherry-picks cleanly to both.
> If you disagree let me know, I could also make a stable-only patch that
> only contains the bug fix part of the mentioned commit.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2025-04-28 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 18:33 stable request: eaaff9b6702e ("netfilter: fib: avoid lookup if socket is available") Florian Westphal
2025-04-28 11:50 ` Greg KH [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=2025042856-skimming-storm-a49b@gregkh \
--to=greg@kroah.com \
--cc=fw@strlen.de \
--cc=linux@slavino.sk \
--cc=pablo@netfilter.org \
--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