From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, Florian Westphal <fw@strlen.de>
Subject: [PATCH 0/2] netfilter: ipset: concurrent add and dump fixes
Date: Wed, 8 Apr 2026 09:02:55 +0200 [thread overview]
Message-ID: <20260408070257.2437291-1-kadlec@netfilter.org> (raw)
Hi Pablo, Florian,
Please consider applying the next patches:
* Fix a data race between add and list in all hash types due to setting
the position index too early.
* Fix a data race between add and list header commands in all hash types
by protecting the list header dumping part as well.
Best regards,
Jozsef
The following changes since commit a9d4f4f6e65e0bf9bbddedecc84d67249991979c:
net/mlx5: Update the list of the PCI supported devices (2026-04-06 19:17:42 -0700)
are available in the Git repository at:
git://blackhole.kfki.hu/nf b93f39a52388ac
for you to fetch changes up to b93f39a52388ac170530633db53137ff7cc41cf3:
netfilter: ipset: Fix data race between add and dump in all hash types (2026-04-08 08:52:31 +0200)
----------------------------------------------------------------
Jozsef Kadlecsik (2):
netfilter: ipset: Fix data race between add and list header in all hash types
netfilter: ipset: Fix data race between add and dump in all hash types
net/netfilter/ipset/ip_set_core.c | 4 ++--
net/netfilter/ipset/ip_set_hash_gen.h | 6 ++++--
2 files changed, 6 insertions(+), 4 deletions(-)
next reply other threads:[~2026-04-08 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 7:02 Jozsef Kadlecsik [this message]
2026-04-08 7:02 ` [PATCH 1/2] netfilter: ipset: Fix data race between add and list header in all hash types Jozsef Kadlecsik
2026-04-08 7:02 ` [PATCH 2/2] netfilter: ipset: Fix data race between add and dump " Jozsef Kadlecsik
2026-04-08 12:35 ` [syzbot ci] Re: netfilter: ipset: concurrent add and dump fixes syzbot ci
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=20260408070257.2437291-1-kadlec@netfilter.org \
--to=kadlec@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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