From: Genes Lists <lists@sapience.com>
To: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.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 07:09:00 -0500 [thread overview]
Message-ID: <67d9f732a55a31f3073675164e8d7ada46da3dbe.camel@sapience.com> (raw)
In-Reply-To: <bb9ab61c-3bed-4c3d-baf0-0bce4e142292@moonlit-rail.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Fri, 2026-02-27 at 01:26 -0500, Kris Karas (Bug Reporting) wrote:
> Greg KH wrote:
> > ...
>
> Bisect complete (from 6.19.3 to 6.19.4)
>
> > e308d4e35ce1e26cd67070a7035ad265662ab9e5 is the first bad commit
> > commit e308d4e35ce1e26cd67070a7035ad265662ab9e5
>
> Kris
>
> P.S. I ran the bisect from 7.0-rc1, so many reboots there, and
> it is fine. The bug only seems to affect 6.x
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
same rules work fine in 6.19.3.
Do you anything similar?
Linux version 7.0.0-rc1-custom-1-00124-g3f4a08e64442 ...
...
In file included from /etc/nftables.conf:134:2-44:
./etc/nftables.d/set_filter.conf:1746:7-21: Error:
Could not process rule: File exists
xx.xxx.xxx.x/23,
^^^^^^^^^^^^^^^
The line falls somewhere in the middle of list of set elements that are
all ip addresses.
Reported here [1]
gene
[1]https://lore.kernel.org/lkml/a529a6a9a2755d45765f20b58c5c11e2f790eacb.camel@sapience.com/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-27 12:09 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 [this message]
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)
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=67d9f732a55a31f3073675164e8d7ada46da3dbe.camel@sapience.com \
--to=lists@sapience.com \
--cc=akpm@linux-foundation.org \
--cc=bugs-a21@moonlit-rail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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®