From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH nft,v2 00/11] replace compound_expr_*() by type safe function
Date: Thu, 21 Aug 2025 11:23:19 +0200 [thread overview]
Message-ID: <20250821092330.2739989-1-pablo@netfilter.org> (raw)
Hi,
This is v2 with minimal changes wrt. previous series.
The aim is to replace (and remove) the existing compound_expr_*()
helper functions which is common to set, list and concat expressions
by expression type safe variants that validate the expression type.
I will hold on with this until nftables 1.1.5 including the fix for
the JSON regression is released.
Pablo Neira Ayuso (11):
src: add expr_type_catchall() helper and use it
src: replace compound_expr_add() by type safe set_expr_add()
src: replace compound_expr_add() by type safe concat_expr_add()
src: replace compound_expr_add() by type safe list_expr_add()
segtree: rename set_compound_expr_add() to set_expr_add_splice()
expression: replace compound_expr_clone() by type safe function
expression: remove compound_expr_add()
expression: replace compound_expr_remove() by type safe function
expression: replace compound_expr_destroy() by type safe funtion
expression: replace compound_expr_print() by type safe function
src: replace compound_expr_alloc() by type safe function
include/expression.h | 15 +++-
src/evaluate.c | 4 +-
src/expression.c | 177 ++++++++++++++++++++++++++------------
src/intervals.c | 20 ++---
src/monitor.c | 2 +-
src/netlink.c | 6 +-
src/netlink_delinearize.c | 8 +-
src/optimize.c | 38 ++++----
src/parser_bison.y | 40 ++++-----
src/parser_json.c | 18 ++--
src/payload.c | 6 +-
src/segtree.c | 40 ++++-----
src/trace.c | 10 +--
13 files changed, 229 insertions(+), 155 deletions(-)
--
2.30.2
next reply other threads:[~2025-08-21 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 9:23 Pablo Neira Ayuso [this message]
2025-08-21 9:23 ` [PATCH nft,v2 01/11] src: add expr_type_catchall() helper and use it Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 02/11] src: replace compound_expr_add() by type safe set_expr_add() Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 03/11] src: replace compound_expr_add() by type safe concat_expr_add() Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 04/11] src: replace compound_expr_add() by type safe list_expr_add() Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 05/11] segtree: rename set_compound_expr_add() to set_expr_add_splice() Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 06/11] expression: replace compound_expr_clone() by type safe function Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 07/11] expression: remove compound_expr_add() Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 08/11] expression: replace compound_expr_remove() by type safe function Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 09/11] expression: replace compound_expr_destroy() by type safe funtion Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 10/11] expression: replace compound_expr_print() by type safe function Pablo Neira Ayuso
2025-08-21 9:23 ` [PATCH nft,v2 11/11] src: replace compound_expr_alloc() " Pablo Neira Ayuso
2025-08-27 22:24 ` [PATCH nft,v2 00/11] replace compound_expr_*() " 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=20250821092330.2739989-1-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).