From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Steven Haigh <netwiz@crc.id.au>
Cc: netfilter@vger.kernel.org
Subject: Re: aarch64 - netlink: Error: Could not process rule: No buffer space available
Date: Wed, 4 Mar 2026 01:35:42 +0100 [thread overview]
Message-ID: <aad-Xq9qYU1QQ0jB@chamomile> (raw)
In-Reply-To: <2a780701-f1e4-4ff4-b796-889f7ee19ead@crc.id.au>
On Wed, Mar 04, 2026 at 11:19:36AM +1100, Steven Haigh wrote:
> Hi Pablo,
>
> Thanks for the reply.
>
> On 4/3/26 11:02, Pablo Neira Ayuso wrote:
> > Hi,
> >
> > On Wed, Mar 04, 2026 at 10:36:20AM +1100, Steven Haigh wrote:
> > > Hi all,
> > >
> > > Firstly, please CC me in replies as I'm not subscribed to the list.
> > >
> > > I am currently loading some named sets into nftables using the following
> > > configuration:
> > >
> > > set au-ipv4 {
> > > type ipv4_addr
> > > flags interval
> > > auto-merge
> > > elements = { $AU.ipv4 }
> > > }
> > >
> > > set au-ipv6 {
> > > type ipv6_addr
> > > flags interval
> > > auto-merge
> > > elements = { $AU.ipv6 }
> > > }
> > >
> > > These sets are loaded in the config via:
> > > include "/etc/nftables/firewall/geo-nft/countrysets/AU.ipv4";
> > > include "/etc/nftables/firewall/geo-nft/countrysets/AU.ipv6";
> > >
> > > The files are created using the geo-nft.sh script here:
> > > https://raw.githubusercontent.com/wirefalls/geo-nft/main/geo-nft.sh
> > >
> > > When loading these, I get the following fatal error:
> > > netlink: Error: Could not process rule: No buffer space available
> > >
> > > This only seems to happen on the aarch64 installs. The same kernel version +
> > > tools version on x86_64 architecture seems to load just fine.
> > >
> > > $ cat /proc/version
> > > Linux version 6.18.15-200.fc43.aarch64
> > > (mockbuild@835a9c7eeabc46d3b99996c22f20c9cf) (gcc (GCC) 15.2.1 20260123 (Red
> > > Hat 15.2.1-7), GNU ld version 2.45.1-4.fc43) #1 SMP PREEMPT_DYNAMIC Fri Feb
> > > 27 22:55:30 UTC 2026
> > >
> > > $ nft --version
> > > nftables v1.1.3 (Commodore Bullmoose #4)
> >
> > Can you try latest nftables version to confirm this bug on aarch64 is
> > current? Otherwise, try nftables git HEAD snapshot?
>
> I grabbed some scratch builds from Fedora 44 which updated:
> * libnftnl 1.2.9 -> 1.3.1
> * nftables 1.1.3 -> 1.1.6
>
> When processing the files though, a new error occurs:
>
> In file included from ./firewall.nft:7:1-61:
> /etc/nftables/firewall/geo-nft/countrysets/AU.ipv4:1646:2-24: Error: Could
> not process rule: File exists
> 103.4.84.0-103.4.87.255,
> ^^^^^^^^^^^^^^^^^^^^^^^
>
> Looking at the ranges at / around this line however, I can't see any kind of
> duplicate:
>
> 103.4.16.0-103.4.19.255,
> 103.4.55.0-103.4.55.255,
> 103.4.60.0-103.4.63.255,
> 103.4.84.0-103.4.87.255,
> 103.4.120.0-103.4.120.255,
> 103.4.122.0-103.4.123.255,
> 103.4.132.0-103.4.133.255,
>
> Checking the datafile:
> $ grep 103.4.84 geo-nft/countrysets/AU.ipv4
> 103.4.84.0-103.4.87.255,
>
> From what I understand, even if this range did overlap - the auto-merge flag
> should handle this.
Are you using the 'create element' command?
This is fixed in git HEAD, this is a bug in 1.1.6.
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.
prev parent reply other threads:[~2026-03-04 0:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 23:36 aarch64 - netlink: Error: Could not process rule: No buffer space available Steven Haigh
2026-03-04 0:02 ` Pablo Neira Ayuso
2026-03-04 0:17 ` Pablo Neira Ayuso
2026-03-04 0:34 ` Steven Haigh
2026-03-04 0:42 ` Pablo Neira Ayuso
2026-03-04 0:49 ` Steven Haigh
2026-03-04 0:53 ` Pablo Neira Ayuso
2026-03-04 1:05 ` Steven Haigh
2026-03-04 1:17 ` Pablo Neira Ayuso
2026-03-04 0:19 ` Steven Haigh
2026-03-04 0:35 ` Pablo Neira Ayuso [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=aad-Xq9qYU1QQ0jB@chamomile \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.org \
--cc=netwiz@crc.id.au \
/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