From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 3/5] mnl: Allow for updating devices on existing inet ingress hook chains
Date: Mon, 8 Sep 2025 12:29:03 +0200 [thread overview]
Message-ID: <aL6v70HMECk3feny@calendula> (raw)
In-Reply-To: <20250829142513.4608-4-phil@nwl.cc>
On Fri, Aug 29, 2025 at 04:25:11PM +0200, Phil Sutter wrote:
> Complete commit a66b5ad9540dd ("src: allow for updating devices on
> existing netdev chain") in supporting inet family ingress hook chains as
> well. The kernel does already but nft has to add a proper hooknum
> attribute to pass the checks.
>
> The hook.num field has to be initialized from hook.name using
> str2hooknum(), which is part of chain evaluation. Calling
> chain_evaluate() just for that purpose is a bit over the top, but the
> hook name lookup may fail and performing chain evaluation for delete
> command as well fits more into the code layout than duplicating parts of
> it in mnl_nft_chain_del() or elsewhere. Just avoid the
> chain_cache_find() call as its assert() triggers when deleting by
> handle and also don't add to be deleted chains to cache.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> src/evaluate.c | 6 ++++--
> src/mnl.c | 2 ++
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/src/evaluate.c b/src/evaluate.c
> index b7e4f71fdfbc9..db4ac18f1dc9f 100644
> --- a/src/evaluate.c
> +++ b/src/evaluate.c
> @@ -5758,7 +5758,9 @@ static int chain_evaluate(struct eval_ctx *ctx, struct chain *chain)
> return table_not_found(ctx);
>
> if (chain == NULL) {
> - if (!chain_cache_find(table, ctx->cmd->handle.chain.name)) {
> + if (ctx->cmd->op != CMD_DELETE &&
> + ctx->cmd->op != CMD_DESTROY &&
> + !chain_cache_find(table, ctx->cmd->handle.chain.name)) {
> chain = chain_alloc();
> handle_merge(&chain->handle, &ctx->cmd->handle);
> chain_cache_add(chain, table);
> @@ -6070,7 +6072,7 @@ static int cmd_evaluate_delete(struct eval_ctx *ctx, struct cmd *cmd)
> return 0;
> case CMD_OBJ_CHAIN:
> chain_del_cache(ctx, cmd);
> - return 0;
> + return chain_evaluate(ctx, cmd->chain);
Maybe fix this to perform chain_del_cache() after chain_evaluate()?
ie.
if (chain_evaluate(ctx, cmd->chain) < 0)
return -1;
chain_del_cache(ctx, cmd);
return 0;
> case CMD_OBJ_TABLE:
> table_del_cache(ctx, cmd);
> return 0;
> diff --git a/src/mnl.c b/src/mnl.c
> index 984dcac27b1cf..d1402c0fcb9f4 100644
> --- a/src/mnl.c
> +++ b/src/mnl.c
> @@ -994,6 +994,8 @@ int mnl_nft_chain_del(struct netlink_ctx *ctx, struct cmd *cmd)
> struct nlattr *nest;
>
> nest = mnl_attr_nest_start(nlh, NFTA_CHAIN_HOOK);
> + mnl_attr_put_u32(nlh, NFTA_HOOK_HOOKNUM,
> + htonl(cmd->chain->hook.num));
> mnl_nft_chain_devs_build(nlh, cmd);
> mnl_attr_nest_end(nlh, nest);
> }
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-09-08 10:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 14:25 [nft PATCH 0/5] Fixes (and fallout) from running tests/monitor in JSON mode Phil Sutter
2025-08-29 14:25 ` [nft PATCH 1/5] tools: gitignore nftables.service file Phil Sutter
2025-08-29 14:25 ` [nft PATCH 2/5] monitor: Quote device names in chain declarations, too Phil Sutter
2025-08-29 14:25 ` [nft PATCH 3/5] mnl: Allow for updating devices on existing inet ingress hook chains Phil Sutter
2025-09-08 10:29 ` Pablo Neira Ayuso [this message]
2025-09-08 11:01 ` Pablo Neira Ayuso
2025-09-08 23:48 ` Phil Sutter
2025-09-09 9:17 ` Pablo Neira Ayuso
2025-08-29 14:25 ` [nft PATCH 4/5] monitor: Inform JSON printer when reporting an object delete event Phil Sutter
2025-09-08 10:30 ` Pablo Neira Ayuso
2025-09-09 11:46 ` Phil Sutter
2025-08-29 14:25 ` [nft PATCH 5/5] tests: monitor: Extend testcases a bit Phil Sutter
2025-09-08 10:30 ` Pablo Neira Ayuso
2025-09-02 10:57 ` [nft PATCH 0/5] Fixes (and fallout) from running tests/monitor in JSON mode Phil Sutter
2025-09-11 16:05 ` Phil Sutter
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=aL6v70HMECk3feny@calendula \
--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