public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Genes Lists <lists@sapience.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	linux-kernel@vger.kernel.org, coreteam@netfilter.org,
	netfilter-devel@vger.kernel.org,
	Pablo Neira Ayuso <pablo@netfilter.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 05:17:32 -0800	[thread overview]
Message-ID: <2026022755-quail-graveyard-93e8@gregkh> (raw)
In-Reply-To: <10537f2b74da2b8a5cb8dc939f723291db39ff84.camel@sapience.com>

On Fri, Feb 27, 2026 at 08:12:59AM -0500, Genes Lists wrote:
> On Fri, 2026-02-27 at 07:23 -0500, Genes Lists wrote:
> > On Fri, 2026-02-27 at 09:00 +0100, Thorsten Leemhuis wrote:
> > > Lo!
> > > 
> > 
> > Repeating the nft error message here for simplicity:
> > 
> >  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,
> >                  ^^^^^^^^^^^^^^^
> > 
> 
> Resolved by updating userspace.
> 
> I can reproduce this error on non-production machine and found this
> error is resolved by re-bulding updated nftables, libmnl and libnftnl:
> 
> With these versions nft rules now load without error:
> 
>  - nftables commit de904e22faa2e450d0d4802e1d9bc22013044f93
>  - libmnl   commit 54dea548d796653534645c6e3c8577eaf7d77411
>  - libnftnl commit 5c5a8385dc974ea7887119963022ae988e2a16cc
> 
> All were compiled on machine running 6.19.4.

Odd, that shouldn't be an issue, as why would the kernel version you
build this on matter?

What about trying commit f175b46d9134 ("netfilter: nf_tables: add
.abort_skip_removal flag for set types")?

thanks,

greg k-h

  reply	other threads:[~2026-02-27 13:17 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     ` [REGRESSION] 6.19.4 stable netfilter / nftables -> resolved Genes Lists
2026-02-27 12:23   ` [REGRESSION] 6.19.4 stable netfilter / nftables Genes Lists
2026-02-27 13:12     ` [REGRESSION] 6.19.4 stable netfilter / nftables [resolved] Genes Lists
2026-02-27 13:17       ` Greg KH [this message]
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=2026022755-quail-graveyard-93e8@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bugs-a21@moonlit-rail.com \
    --cc=coreteam@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@sapience.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox