From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 2/2] tests: shell: expand get command test with open intervals
Date: Tue, 7 Jul 2026 16:16:01 +0200 [thread overview]
Message-ID: <ak0KITUOuYAXYm5v@chamomile> (raw)
In-Reply-To: <akz-fH24aKQbjaHm@orbyte.nwl.cc>
Hi Phil,
On Tue, Jul 07, 2026 at 03:26:20PM +0200, Phil Sutter wrote:
> Hi Pablo,
> On Thu, Jul 02, 2026 at 02:36:34PM +0200, Pablo Neira Ayuso wrote:
> > Extend the existing test to cover get commands with open internals.
>
> This test fails on a Big Endian testing machine running Fedora Rawhide
> running 7.2.0-0.rc2.21.fc45. Does this perhaps test a recent kernel fix
> or something?
Does this kernel contain this kernel fix?
https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=d63611cbe8af99dd61b118ee6e5b5e3e518250b2
as well as this userspace fix:
https://git.netfilter.org/nftables/commit/?id=4eafc1a2a9ef5a827b1b4e58cb3b2832d2eb1650
> Here's the test output for reference:
>
> | W: [FAILED] 1/1 testcases/sets/0034get_element_0
> | Command: testcases/sets/0034get_element_0
> | Error: Could not process rule: No such file or directory
> | get element ip t s { 11 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: No such file or directory
> | get element ip t s { 15-18 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: Too many open files
> | get element ip t s { 60000-65534 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | ERROR: asked for '60000-65534' in set s, expecting '60000-65535' but got
> | ''
> | Error: Could not process rule: Too many open files
> | get element ip t s { 60001-65534 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | ERROR: asked for '60001-65534' in set s, expecting '60000-65535' but got
> | ''
> | Error: Could not process rule: Too many open files
> | get element ip t s { 22-24, 60000-65534 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | ERROR: asked for '22-24, 60000-65534' in set s, expecting '20-30,
> | 60000-65535' but got ''
> | Error: Could not process rule: Too many open files
> | get element ip t s { 22-24, 60001-65534 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | ERROR: asked for '22-24, 60001-65534' in set s, expecting '20-30,
> | 60000-65535' but got ''
> | Error: Could not process rule: Too many open files
> | get element ip t s { 60001-65534, 10 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | ERROR: asked for '60001-65534, 10' in set s, expecting '60000-65535, 10'
> | but got ''
> | Error: Could not process rule: No such file or directory
> | get element ip t s { 10-40 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: No such file or directory
> | get element ip t s { 10-20 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: No such file or directory
> | get element ip t s { 10-25 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: No such file or directory
> | get element ip t s { 25-55 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: No such file or directory
> | get element ip t ips { 10.0.0.2 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: No such file or directory
> | get element ip t cs { 10.0.0.1 . 23 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | Error: Could not process rule: No such file or directory
> | get element ip t cs { 10.0.0.2 . 22 }
> | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Cheers, Phil
next prev parent reply other threads:[~2026-07-07 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:36 [PATCH nft 1/2] segtree: fix get element command with open intervals Pablo Neira Ayuso
2026-07-02 12:36 ` [PATCH nft 2/2] tests: shell: expand get command test " Pablo Neira Ayuso
2026-07-07 13:26 ` Phil Sutter
2026-07-07 14:16 ` Pablo Neira Ayuso [this message]
2026-07-07 14:49 ` Phil Sutter
2026-07-07 14:52 ` 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=ak0KITUOuYAXYm5v@chamomile \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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