All of lore.kernel.org
 help / color / mirror / Atom feed
From: Genes Lists <lists@sapience.com>
To: Florian Westphal <fw@strlen.de>,
	Thorsten Leemhuis <regressions@leemhuis.info>
Cc: 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 -> resolved
Date: Fri, 27 Feb 2026 13:58:52 -0500	[thread overview]
Message-ID: <06b6a53bff1a5db07a29dec6441995d97b20cfa5.camel@sapience.com> (raw)
In-Reply-To: <aaFSOkhkjowYB2YJ@strlen.de>

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

On Fri, 2026-02-27 at 09:13 +0100, Florian Westphal wrote:
> 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.

Summary now that all is resolved.

There were, coincidently, 2 separate issues.
Pure serendipity they happened together.

 a) kernel 6.19.4 netfilter oops [1]
    which is fixed by   
	f175b46d9134f708358b5404730c6dfa200fbf3c
 
 b) nftables with large sets 
    nft reports spurious error:
    rule could not be loaded: File exists
    After which no rules are loaded.

    Fixed in nftables git repo 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 happens with kernels :
    - 6.19.4 + netfilter commit f175b46d9134f7
    - 7.0-rc1
    - linux-next
 
    It does not seem to happen with older kernels (assuming I 
    did not mess up the testing!)

    I confirmed this 2nd issue is resolved in both 
    - nftables git head and
    - v1.1.6 plus
      git cherry-pick \
       a9ead6a808dbe637ae7b9f54598f0dff9582d34d \
       e83e32c8d1cd228d751fb92b756306c6eb6c0759


thanks all.

gene


[1] 
https://lore.kernel.org/all/bb9ab61c-3bed-4c3d-baf0-0bce4e142292@moonlit-rail.com/

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

  reply	other threads:[~2026-02-27 18:58 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
2026-02-27 18:58     ` Genes Lists [this message]
2026-02-27 12:23   ` 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=06b6a53bff1a5db07a29dec6441995d97b20cfa5.camel@sapience.com \
    --to=lists@sapience.com \
    --cc=bugs-a21@moonlit-rail.com \
    --cc=coreteam@netfilter.org \
    --cc=fw@strlen.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.