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 10:47:33 +0100 [thread overview]
Message-ID: <ZcCutfqrH/SHlaRw@calendula> (raw)
In-Reply-To: <2_5uNX_sumsVU038csU_coYap0tNQR6gTiA1GDY4Onp16EhEPGkvRE80rAwirPIiGCn9eVKjFNzc8D_zQG98pDys1uxfCIeYh6k3KG6jGXU=@proton.me>
On Sat, Feb 03, 2024 at 03:49:54PM +0000, Eric wrote:
> On Friday, February 2nd, 2024 at 01:23, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > Works fine with -stable 5.15 and 6.1 here.
> >
> > Does your kernel turn on this?
> >
> > CONFIG_NETFILTER_NETLINK_HOOK=m
>
> Like Slavko, my test devices (both OpenWrt builds) have
>
> # CONFIG_NETFILTER_NETLINK_HOOK is not set
>
> I'll have to check and see how much it grows the kernel when enabled, as this
> seems like it would be useful to have on by default.
It should not take much, it is a simple netlink interface that
iterates over a few existing datastructures.
> Re the seg fault, I'm still trying to find a minimal reproducer, but it looks
> like just about anything fires it off with k5.15 (I see it on x86, MIPS and
> aarch64 devices).
Strange that userspace crashes depending on the kernel version.
What is your userspace nft version there?
Thanks.
next prev parent reply other threads:[~2024-02-05 9:47 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 [this message]
2024-02-05 17:02 ` Eric
2024-02-05 17:08 ` Pablo Neira Ayuso
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=ZcCutfqrH/SHlaRw@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 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.