From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Slavko <linux@slavino.sk>, netfilter ML <netfilter@vger.kernel.org>
Subject: Re: nftables RP filter and loopback
Date: Wed, 23 Apr 2025 22:58:45 +0200 [thread overview]
Message-ID: <aAlUhaH8ryNauGe9@calendula> (raw)
In-Reply-To: <aAlUBmTljaz3bD-L@calendula>
On Wed, Apr 23, 2025 at 10:56:41PM +0200, Pablo Neira Ayuso wrote:
> On Wed, Apr 23, 2025 at 02:06:05PM +0200, Florian Westphal wrote:
> > Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > > Yes, I didn't notice either. Anyway, unless you can forecast any
> > > issue, I'd suggest to backport the entire patch? IIRC patch is
> > > relatively small and keeping it in sync with main could possibly help
> > > with cherrypicking fixes.
> >
> > Right, it would keep -stable "bug compatible" too.
> >
> > Maybe its ok to ask to cherry-pick it as is for
> > 6.14 and 6.12.
>
> OK, let's request this cherry-pick for 6.12. Thanks
eaaff9b6702e ("netfilter: fib: avoid lookup if socket is available")
> > 6.13 is EOL already, 6.12 is longterm.
> >
> > This would leave 6.6 and 6.1 longterm out but from lack
> > of bug reports so far I would not say its a prominent bug.
> >
> > The upstream patch cherry-picks for all except 6.1.y, but
> > AFAICS its just a simple context conflict.
> >
> > Earlier longterm kernels aren't affected.
next prev parent reply other threads:[~2025-04-23 20:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 8:49 nftables RP filter and loopback Slavko
2025-04-22 11:43 ` Florian Westphal
2025-04-22 12:32 ` Slavko
2025-04-22 12:53 ` Florian Westphal
2025-04-22 13:15 ` Slavko
2025-04-22 14:15 ` Pablo Neira Ayuso
2025-04-23 9:10 ` Florian Westphal
2025-04-23 11:51 ` Pablo Neira Ayuso
2025-04-23 12:06 ` Florian Westphal
2025-04-23 20:56 ` Pablo Neira Ayuso
2025-04-23 20:58 ` Pablo Neira Ayuso [this message]
2025-04-26 8:39 ` Slavko
2025-04-26 9:24 ` Florian Westphal
2025-04-26 9:40 ` Slavko
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=aAlUhaH8ryNauGe9@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=linux@slavino.sk \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.