mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 16:20:24 -0500	[thread overview]
Message-ID: <e6b43861cda6953cc7f8c259e663b890e53d7785.camel@sapience.com> (raw)
In-Reply-To: <8909a57e-22ca-427d-8d41-cbd68895d33e@moonlit-rail.com>

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

On Fri, 2026-02-27 at 16:01 -0500, Kris Karas (Bug Reporting) wrote:
> Genes Lists wrote:
> 
> 
> 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

Thanks Kris, I'll try help clarify. Things weren't crystal clear at
first.

There were actually 2 separate issues that happened to hit at the same
time.

 (1) the 6.19.4 netfilter crash 
     Now fixed or will be shortly in 6.19.5.

and 

 (2) a userspace issue with nft v1.1.6 and large sets leading to 
     spurious 'file exists' errors. 
     This has nothing at all to do with any kernel oops.

     This 2nd issue has been fixed in nftables by commit: 

  ---
    commit e83e32c8d1cd228d751fb92b756306c6eb6c0759
    Author: Pablo Neira Ayuso <pablo@netfilter.org>
    Date:   Mon Jan 12 12:59:26 2026 +0100

    mnl: restore create element command with large batches
    
    The rework to reduce memory consumption has introduced a
    bug that result in spurious EEXIST with large batches.
    ---

This commit came after nftables v1.1.6 release.
Rebuilding nftables with this commit sorts out the 2nd (userspace)
issue.

gene



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

      reply	other threads:[~2026-02-27 21:20 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)
2026-02-27 21:20           ` Genes Lists [this message]

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=e6b43861cda6953cc7f8c259e663b890e53d7785.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®