From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Kyle Zeng <zengyhkyle@gmail.com>
Subject: [PATCH 0/1] ipset patch for nf tree
Date: Tue, 19 Sep 2023 20:04:44 +0200 [thread overview]
Message-ID: <20230919180445.3384561-1-kadlec@netfilter.org> (raw)
Hi Pablo,
Please apply the next patch against your nf tree so that it'll get
applied to older stable branches too.
- Kyle Zeng reported that there is a race between IPSET_CMD_ADD and IPSET_CMD_SWAP:
when the schedule point was added to call_ad(), the wrong reference counter was
used. For long taking operations initiated from userspace the ref_netlink reference
counter must be used to exclude concurrent clashing operations.
Best regards,
Jozsef
The following changes since commit 7153a404fb70d21097af3169354e1e5fda3fbb02:
Merge tag 'nf-23-09-06' of https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf (2023-09-07 11:47:15 +0200)
are available in the Git repository at:
git://blackhole.kfki.hu/nf 5adf434ae86e34a0c
for you to fetch changes up to 5adf434ae86e34a0cff2fd0aa737dab16d7f4812:
netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP (2023-09-19 12:34:45 +0200)
----------------------------------------------------------------
Jozsef Kadlecsik (1):
netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP
net/netfilter/ipset/ip_set_core.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
next reply other threads:[~2023-09-19 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 18:04 Jozsef Kadlecsik [this message]
2023-09-19 18:04 ` [PATCH 1/1] netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP Jozsef Kadlecsik
2023-09-19 20:50 ` [PATCH 0/1] ipset patch for nf tree Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2024-06-04 13:58 Jozsef Kadlecsik
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=20230919180445.3384561-1-kadlec@netfilter.org \
--to=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zengyhkyle@gmail.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;
as well as URLs for NNTP newsgroup(s).