From: Lee Jones <lee@kernel.org>
To: lee@kernel.org, stable@vger.kernel.org
Cc: pablo@netfilter.org, fw@strlen.de, Lee Jones <joneslee@google.com>
Subject: [PATCH 4/5] netfilter: nft_set_hash: mark set element as dead when deleting from packet path
Date: Tue, 19 Sep 2023 17:44:32 +0100 [thread overview]
Message-ID: <20230919164437.3297021-5-lee@kernel.org> (raw)
In-Reply-To: <20230919164437.3297021-1-lee@kernel.org>
From: Pablo Neira Ayuso <pablo@netfilter.org>
[ Upstream commit c92db3030492b8ad1d0faace7a93bbcf53850d0c ]
Set on the NFT_SET_ELEM_DEAD_BIT flag on this element, instead of
performing element removal which might race with an ongoing transaction.
Enable gc when dynamic flag is set on since dynset deletion requires
garbage collection after this patch.
Fixes: d0a8d877da97 ("netfilter: nft_dynset: support for element deletion")
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Signed-off-by: Lee Jones <joneslee@google.com>
---
net/netfilter/nft_set_hash.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/net/netfilter/nft_set_hash.c b/net/netfilter/nft_set_hash.c
index 2f067e4596b02..cef5df8460009 100644
--- a/net/netfilter/nft_set_hash.c
+++ b/net/netfilter/nft_set_hash.c
@@ -249,7 +249,9 @@ static bool nft_rhash_delete(const struct nft_set *set,
if (he == NULL)
return false;
- return rhashtable_remove_fast(&priv->ht, &he->node, nft_rhash_params) == 0;
+ nft_set_elem_dead(&he->ext);
+
+ return true;
}
static void nft_rhash_walk(const struct nft_ctx *ctx, struct nft_set *set,
@@ -412,7 +414,7 @@ static int nft_rhash_init(const struct nft_set *set,
return err;
INIT_DEFERRABLE_WORK(&priv->gc_work, nft_rhash_gc);
- if (set->flags & NFT_SET_TIMEOUT)
+ if (set->flags & (NFT_SET_TIMEOUT | NFT_SET_EVAL))
nft_rhash_gc_init(set);
return 0;
--
2.42.0.459.ge4e396fd5e-goog
next prev parent reply other threads:[~2023-09-19 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 16:44 [PATCH 0/5] netfilter: Reinstate dropped Stable patches Lee Jones
2023-09-19 16:44 ` [PATCH 1/5] netfilter: nf_tables: don't skip expired elements during walk Lee Jones
2023-09-19 16:44 ` [PATCH 2/5] netfilter: nf_tables: GC transaction API to avoid race with control plane Lee Jones
2023-09-19 16:44 ` [PATCH 3/5] netfilter: nf_tables: adapt set backend to use GC transaction API Lee Jones
2023-09-19 16:44 ` Lee Jones [this message]
2023-09-19 16:44 ` [PATCH 5/5] netfilter: nf_tables: remove busy mark and gc batch API Lee Jones
2023-09-19 16:49 ` [PATCH 0/5] netfilter: Reinstate dropped Stable patches Pablo Neira Ayuso
2023-09-19 16:51 ` Pablo Neira Ayuso
2023-09-20 9:29 ` Lee Jones
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=20230919164437.3297021-5-lee@kernel.org \
--to=lee@kernel.org \
--cc=fw@strlen.de \
--cc=joneslee@google.com \
--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