From: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>
To: Genes Lists <lists@sapience.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, jslaby@suse.cz,
linux-kernel@vger.kernel.org, lwn@lwn.net,
stable@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 6.19.4 - Oops, regression
Date: Fri, 27 Feb 2026 16:01:18 -0500 [thread overview]
Message-ID: <8909a57e-22ca-427d-8d41-cbd68895d33e@moonlit-rail.com> (raw)
In-Reply-To: <67d9f732a55a31f3073675164e8d7ada46da3dbe.camel@sapience.com>
Genes Lists wrote:
> In my case, 7.0-rc1 also boots just fine, but when attempting to load
> the nftables rules, nft gives an error and rules are not loaded.
The nftables rules with "sets" load fine for me under 7.0-rc1 here on my
desktop/development machine, the one which gave me all the problems.
That said, my largest set here is only 35 elements in size.
My version of nftables is 1.1.6 (from Slackware64-current).
> Resolved by rebuilding userspace nftables on 6.19.4.
>
> - nftables commit de904e22faa2e450d0d4802e1d9bc22013044f93
> - libmnl commit 54dea548d796653534645c6e3c8577eaf7d77411
> - libnftnl commit 5c5a8385dc974ea7887119963022ae988e2a16cc
I second Greg's comment - "Odd" - in wondering why you need to patch
userspace and/or recompile it if the same userspace was working fine on
6.19.3?
FWIW, nftables 1.1.6 (libnftnl 1.3.1, libmnl 1.0.5) is still working
fine for me under 6.19.4 using the .abort_skip_removal patches from
Pablo as forwarded by Greg.
Kris
next prev parent reply other threads:[~2026-02-27 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 23:14 Linux 6.19.4 Greg Kroah-Hartman
2026-02-26 23:14 ` Greg Kroah-Hartman
2026-02-27 4:46 ` Linux 6.19.4 - Oops, regression Kris Karas (Bug Reporting)
2026-02-27 4:56 ` Greg KH
2026-02-27 5:27 ` Kris Karas (Bug Reporting)
2026-02-27 6:26 ` Kris Karas (Bug Reporting)
2026-02-27 12:09 ` Genes Lists
2026-02-27 13:18 ` Genes Lists
2026-02-27 13:32 ` Greg KH
2026-02-27 13:59 ` Genes Lists
2026-02-27 14:44 ` Genes Lists
2026-02-27 18:51 ` Philip Müller
2026-02-27 20:17 ` Greg KH
2026-02-27 21:01 ` Kris Karas (Bug Reporting) [this message]
2026-02-27 21:20 ` Genes Lists
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=8909a57e-22ca-427d-8d41-cbd68895d33e@moonlit-rail.com \
--to=bugs-a21@moonlit-rail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@sapience.com \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®