From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ziyang Xuan <william.xuanziyang@huawei.com>
Cc: kadlec@netfilter.org, netfilter-devel@vger.kernel.org, fw@strlen.de
Subject: Re: [PATCH nft 2/2] netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get()
Date: Thu, 11 Apr 2024 12:05:47 +0200 [thread overview]
Message-ID: <Zhe1-4M2ObeQGEYz@calendula> (raw)
In-Reply-To: <ab7c6584a047d80a9c4658a4d196b555567642e4.1712472595.git.william.xuanziyang@huawei.com>
On Sun, Apr 07, 2024 at 02:56:05PM +0800, Ziyang Xuan wrote:
> nft_unregister_obj() can concurrent with __nft_obj_type_get(),
> and there is not any protection when iterate over nf_tables_objects
> list in __nft_obj_type_get(). Therefore, there is pertential
> data-race of nf_tables_objects list entry.
>
> Use list_for_each_entry_rcu() to iterate over nf_tables_objects
> list in __nft_obj_type_get(), and use rcu_read_lock() in the caller
> nft_obj_type_get() to protect the entire type query process.
Also applied, thanks
> Fixes: e50092404c1b ("netfilter: nf_tables: add stateful objects")
> Signed-off-by: Ziyang Xuan <william.xuanziyang@huawei.com>
> ---
> net/netfilter/nf_tables_api.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/net/netfilter/nf_tables_api.c b/net/netfilter/nf_tables_api.c
> index 646d59685cfd..70fe0ca24d34 100644
> --- a/net/netfilter/nf_tables_api.c
> +++ b/net/netfilter/nf_tables_api.c
> @@ -7607,7 +7607,7 @@ static const struct nft_object_type *__nft_obj_type_get(u32 objtype, u8 family)
> {
> const struct nft_object_type *type;
>
> - list_for_each_entry(type, &nf_tables_objects, list) {
> + list_for_each_entry_rcu(type, &nf_tables_objects, list) {
> if (type->family != NFPROTO_UNSPEC &&
> type->family != family)
> continue;
> @@ -7623,9 +7623,13 @@ nft_obj_type_get(struct net *net, u32 objtype, u8 family)
> {
> const struct nft_object_type *type;
>
> + rcu_read_lock();
> type = __nft_obj_type_get(objtype, family);
> - if (type != NULL && try_module_get(type->owner))
> + if (type != NULL && try_module_get(type->owner)) {
> + rcu_read_unlock();
> return type;
> + }
> + rcu_read_unlock();
>
> lockdep_nfnl_nft_mutex_not_held();
> #ifdef CONFIG_MODULES
> --
> 2.25.1
>
prev parent reply other threads:[~2024-04-11 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 6:56 [PATCH nft 0/2] netfilter: nf_tables: Use rcu lock to enhance protection of the lists Ziyang Xuan
2024-04-07 6:56 ` [PATCH nft 1/2] netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() Ziyang Xuan
2024-04-11 10:04 ` Pablo Neira Ayuso
2024-04-07 6:56 ` [PATCH nft 2/2] netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() Ziyang Xuan
2024-04-11 10:05 ` Pablo Neira Ayuso [this message]
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=Zhe1-4M2ObeQGEYz@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=william.xuanziyang@huawei.com \
/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