From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric <evil.function@proton.me>
Cc: Slavko <linux@slavino.sk>, Netfilter list <netfilter@vger.kernel.org>
Subject: Re: Combine ipv4 and ipv6 in a set
Date: Mon, 5 Feb 2024 18:08:55 +0100 [thread overview]
Message-ID: <ZcEWJ8U08NuqxHgc@calendula> (raw)
In-Reply-To: <clHlpumTk0UKqy_54SFkWToltmb6w40b0TQh2_xQ9h0WwoGFYXvEWUCiXhSvBV5h8elVzIlVTkYSMInXDLfaYt9QP9tVeqfoQxXTyXR0Yk4=@proton.me>
On Mon, Feb 05, 2024 at 05:02:16PM +0000, Eric wrote:
> On Monday, February 5th, 2024 at 01:47, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>
> > Strange that userspace crashes depending on the kernel version.
> >
> > What is your userspace nft version there?
>
> This is on the current release of OpenWrt so previous release of nft. Same behavior on x86, aarch64 and mips. All other commands from my monkey testing just return silently, only this one fails.
>
> $ uname -a
> Linux rtr00 5.15.137 #0 SMP Tue Nov 14 13:38:11 2023 x86_64 GNU/Linux
>
> $ nft -V
> nftables v1.0.8 (Old Doc Yak #2)
> cli: no
> json: yes
> minigmp: yes
> libxtables: no
>
> $ nft list ct expectation table inet fw4
> Segmentation fault
Fix is already available in v1.0.9:
commit a8ff324dc64fd76f7d218d3d94c5885250951258
Author: Florian Westphal <fw@strlen.de>
Date: Fri Jul 28 21:04:13 2023 +0200
ct expectation: fix 'list object x' vs. 'list objects in table' confusion
Just like "ct timeout", "ct expectation" is in need of the same fix,
we get segfault on "nft list ct expectation table t", if table t exists.
This is the exact same pattern as resolved for "ct timeout" in commit
1d2e22fc0521 ("ct timeout: fix 'list object x' vs. 'list objects in table' confusion").
Signed-off-by: Florian Westphal <fw@strlen.de>
next prev parent reply other threads:[~2024-02-05 17:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 10:17 Combine ipv4 and ipv6 in a set Daniel
2024-01-30 10:39 ` Kerin Millar
2024-01-30 12:13 ` Daniel
2024-01-30 12:59 ` Daniel
2024-01-30 13:08 ` Marc Haber
2024-01-30 13:22 ` Kim B. Heino
2024-01-31 10:21 ` Marc Haber
2024-01-31 11:22 ` Kim B. Heino
2024-01-30 15:17 ` Kerin Millar
2024-01-30 17:00 ` Slavko
2024-01-30 17:57 ` Kerin Millar
2024-01-30 19:34 ` Slavko
2024-01-30 22:05 ` Kerin Millar
2024-02-01 12:13 ` Marc Haber
2024-01-31 11:27 ` Marc Haber
2024-01-31 11:13 ` Marc Haber
2024-01-31 11:00 ` Marc Haber
2024-01-31 10:54 ` Marc Haber
2024-01-31 11:55 ` Daniel
2024-02-01 11:39 ` Marc Haber
2024-01-31 13:02 ` Kerin Millar
2024-01-31 20:23 ` Slavko
2024-01-31 22:10 ` Kerin Millar
2024-02-01 6:06 ` Kevin P. Fleming
2024-02-01 17:09 ` Kerin Millar
2024-02-01 10:50 ` Slavko
2024-02-01 12:48 ` Kerin Millar
2024-02-01 13:42 ` Slavko
2024-02-01 14:03 ` Kerin Millar
2024-01-31 22:36 ` Pablo Neira Ayuso
2024-02-01 8:22 ` Slavko
2024-02-02 1:38 ` Eric
2024-02-02 9:23 ` Pablo Neira Ayuso
2024-02-03 9:24 ` Slavko
2024-02-03 15:49 ` Eric
2024-02-05 9:47 ` Pablo Neira Ayuso
2024-02-05 17:02 ` Eric
2024-02-05 17:08 ` Pablo Neira Ayuso [this message]
2024-02-05 17:16 ` Eric
2024-02-01 11:33 ` Marc Haber
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=ZcEWJ8U08NuqxHgc@calendula \
--to=pablo@netfilter.org \
--cc=evil.function@proton.me \
--cc=linux@slavino.sk \
--cc=netfilter@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