From: Florian Westphal <fw@strlen.de>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Genes Lists <lists@sapience.com>,
linux-kernel@vger.kernel.org, coreteam@netfilter.org,
netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, regressions@lists.linux.dev,
"Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
Subject: Re: [REGRESSION] 6.19.4 stable netfilter / nftables
Date: Fri, 27 Feb 2026 09:13:46 +0100 [thread overview]
Message-ID: <aaFSOkhkjowYB2YJ@strlen.de> (raw)
In-Reply-To: <45f03b0b-fe8f-4942-bad1-3fbde03d4be1@leemhuis.info>
Thorsten Leemhuis <regressions@leemhuis.info> wrote:
> On 2/27/26 04:46, Genes Lists wrote:
> > I have a problem with nftables not working on 6.19.4
>
> Thx for the report. A problem that from a brief look seems to be similar
> ist already discussed and was bisected in this thread:
>
> https://lore.kernel.org/all/bb9ab61c-3bed-4c3d-baf0-0bce4e142292@moonlit-rail.com/
Thanks for this pointer.
Can someone check if 'git cherry-pick f175b46d9134f708358b5404730c6dfa200fbf3c'
makes things work again post 6.19.4?
Its a missing indirect dependency.
next prev parent reply other threads:[~2026-02-27 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 3:46 [REGRESSION] 6.19.4 stable netfilter / nftables Genes Lists
2026-02-27 8:00 ` Thorsten Leemhuis
2026-02-27 8:13 ` Florian Westphal [this message]
2026-02-27 18:58 ` [REGRESSION] 6.19.4 stable netfilter / nftables -> resolved Genes Lists
2026-02-27 12:23 ` [REGRESSION] 6.19.4 stable netfilter / nftables Genes Lists
2026-02-27 13:12 ` [REGRESSION] 6.19.4 stable netfilter / nftables [resolved] Genes Lists
2026-02-27 13:17 ` Greg KH
2026-02-27 13:39 ` Genes Lists
2026-03-03 7:00 ` Jindrich Makovicka
2026-03-03 7:31 ` Thorsten Leemhuis
2026-03-03 17:32 ` Jindrich Makovicka
2026-03-03 18:44 ` Florian Westphal
2026-03-03 22:03 ` Pablo Neira Ayuso
2026-03-04 5:50 ` Thorsten Leemhuis
2026-03-04 11:09 ` Pablo Neira Ayuso
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=aaFSOkhkjowYB2YJ@strlen.de \
--to=fw@strlen.de \
--cc=bugs-a21@moonlit-rail.com \
--cc=coreteam@netfilter.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@sapience.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--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 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.