mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Genes Lists <lists@sapience.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Kris Karas (Bug Reporting)" <bugs-a21@moonlit-rail.com>,
	 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 08:59:28 -0500	[thread overview]
Message-ID: <95fea1bd0ded180bb79285ec8416053c614150f8.camel@sapience.com> (raw)
In-Reply-To: <2026022750-everyone-huff-8fd0@gregkh>

[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]

On Fri, 2026-02-27 at 08:32 -0500, Greg KH wrote:
> On Fri, Feb 27, 2026 at 08:18:52AM -0500, Genes Lists wrote:
> > On Fri, 2026-02-27 at 07:09 -0500, Genes Lists wrote:
> > > On Fri, 2026-02-27 at 01:26 -0500, Kris Karas (Bug Reporting)
> > > wrote:
> > > > Greg KH wrote:
> > > > > 
> > > 
> > >   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
> > 
> > Sorry for noise, not kernel related.
> > Resolved by updated userspace.
> > 
> > Resolved by rebuilding userspace nftables on 6.19.4. 
> > I used git head for all.
> > 
> >  nft rules now load without error using:
> > 
> >  - nftables commit de904e22faa2e450d0d4802e1d9bc22013044f93
> >  - libmnl   commit 54dea548d796653534645c6e3c8577eaf7d77411
> >  - libnftnl commit 5c5a8385dc974ea7887119963022ae988e2a16cc
> 
> Yet 7.0-rc1 worked just fine?  That feels wrong...

Sorry if was not clear.  Only 6.19.4 has kernel crash. 
The summary is:

 - 7.0-rc1 - no kernel issues
    boots fine and does not crash when nftables is invoked.  
    But, It has an nft error and fails to load rules with
    older nftables userspace.
    Same rules load fine using updated nftables.

- 6.19.4 - crashes whenever nftables is invoked.
  Does not matter which userspace nftables is used, older or newer

- 6.19.3 - works fine.

I will report back soon as have finished testing 6.19.4 with commit
f175b46d9134

gene

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-02-27 13:59 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 [this message]
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=95fea1bd0ded180bb79285ec8416053c614150f8.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®