From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH -stable,6.1 1/3] netfilter: nf_tables: pass nft_chain to destroy function, not nft_ctx
Date: Tue, 20 May 2025 09:42:55 -0400 [thread overview]
Message-ID: <20250520063816-41ba984eaddb5b28@stable.kernel.org> (raw)
In-Reply-To: <20250519233438.22640-2-pablo@netfilter.org>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 8965d42bcf54d42cbc72fe34a9d0ec3f8527debd
WARNING: Author mismatch between patch and upstream commit:
Backport author: Pablo Neira Ayuso<pablo@netfilter.org>
Commit author: Florian Westphal<fw@strlen.de>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 825a80817cf1)
Note: The patch differs from the upstream commit:
---
1: 8965d42bcf54d ! 1: ef035fe6fb396 netfilter: nf_tables: pass nft_chain to destroy function, not nft_ctx
@@ Metadata
## Commit message ##
netfilter: nf_tables: pass nft_chain to destroy function, not nft_ctx
+ commit 8965d42bcf54d42cbc72fe34a9d0ec3f8527debd upstream.
+
It would be better to not store nft_ctx inside nft_trans object,
the netlink ctx strucutre is huge and most of its information is
never needed in places that use trans->ctx.
@@ Commit message
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
+ Stable-dep-of: c03d278fdf35 ("netfilter: nf_tables: wait for rcu grace period on net_device removal")
+ Signed-off-by: Sasha Levin <sashal@kernel.org>
## include/net/netfilter/nf_tables.h ##
@@ include/net/netfilter/nf_tables.h: static inline bool nft_chain_is_bound(struct nft_chain *chain)
@@ net/netfilter/nf_tables_api.c: static int nf_tables_addchain(struct nft_ctx *ctx
return err;
}
@@ net/netfilter/nf_tables_api.c: static void nft_commit_release(struct nft_trans *trans)
- if (nft_trans_chain_update(trans))
- nft_hooks_destroy(&nft_trans_chain_hooks(trans));
- else
-- nf_tables_chain_destroy(&trans->ctx);
-+ nf_tables_chain_destroy(nft_trans_chain(trans));
+ kfree(nft_trans_chain_name(trans));
+ break;
+ case NFT_MSG_DELCHAIN:
+- nf_tables_chain_destroy(&trans->ctx);
++ nf_tables_chain_destroy(nft_trans_chain(trans));
break;
case NFT_MSG_DELRULE:
- case NFT_MSG_DESTROYRULE:
+ nf_tables_rule_destroy(&trans->ctx, nft_trans_rule(trans));
@@ net/netfilter/nf_tables_api.c: static void nf_tables_abort_release(struct nft_trans *trans)
- if (nft_trans_chain_update(trans))
- nft_hooks_destroy(&nft_trans_chain_hooks(trans));
- else
-- nf_tables_chain_destroy(&trans->ctx);
-+ nf_tables_chain_destroy(nft_trans_chain(trans));
+ nf_tables_table_destroy(&trans->ctx);
+ break;
+ case NFT_MSG_NEWCHAIN:
+- nf_tables_chain_destroy(&trans->ctx);
++ nf_tables_chain_destroy(nft_trans_chain(trans));
break;
case NFT_MSG_NEWRULE:
nf_tables_rule_destroy(&trans->ctx, nft_trans_rule(trans));
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-05-20 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 23:34 [PATCH -stable,6.1 0/3] Netfilter fixes for -stable Pablo Neira Ayuso
2025-05-19 23:34 ` [PATCH -stable,6.1 1/3] netfilter: nf_tables: pass nft_chain to destroy function, not nft_ctx Pablo Neira Ayuso
2025-05-20 13:42 ` Sasha Levin [this message]
2025-05-19 23:34 ` [PATCH -stable,6.1 2/3] netfilter: nf_tables: wait for rcu grace period on net_device removal Pablo Neira Ayuso
2025-05-20 13:36 ` Sasha Levin
2025-05-19 23:34 ` [PATCH -stable,6.1 3/3] netfilter: nf_tables: do not defer rule destruction via call_rcu Pablo Neira Ayuso
2025-05-20 13:40 ` Sasha Levin
2025-05-20 11:09 ` [PATCH -stable,6.1 0/3] Netfilter fixes for -stable Greg KH
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=20250520063816-41ba984eaddb5b28@stable.kernel.org \
--to=sashal@kernel.org \
--cc=pablo@netfilter.org \
--cc=stable@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