From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [PATCH 0/2] ipset patches for nf
Date: Fri, 30 Dec 2022 13:24:36 +0100 [thread overview]
Message-ID: <20221230122438.1618153-1-kadlec@netfilter.org> (raw)
Hi Pablo,
Please pull the next patches into your nf tree.
- The first patch fixes a hang when 0/0 subnets is added to a
hash:net,port,net type of set. Except hash:net,port,net and
hash:net,iface, the set types don't support 0/0 and the auxiliary
functions rely on this fact. So 0/0 needs a special handling in
hash:net,port,net which was missing (hash:net,iface was not affected
by this bug).
- When adding/deleting large number of elements in one step in ipset,
it can take a reasonable amount of time and can result in soft lockup
errors. This patch is a complete rework of the previous version in order
to use a smaller internal batch limit and at the same time removing
the external hard limit to add arbitrary number of elements in one step.
Please note, while the second patch removes half of the first patch, the
remaining part of the first patch is still important.
Best regards,
Jozsef
The following changes since commit 123b99619cca94bdca0bf7bde9abe28f0a0dfe06:
netfilter: nf_tables: honor set timeout and garbage collection updates (2022-12-22 10:36:37 +0100)
are available in the Git repository at:
git://blackhole.kfki.hu/nf 82f6ab0989c5aa14e
for you to fetch changes up to 82f6ab0989c5aa14e89f2689f47f89589733f2b2:
netfilter: ipset: Rework long task execution when adding/deleting entries (2022-12-30 13:11:23 +0100)
----------------------------------------------------------------
Jozsef Kadlecsik (2):
netfilter: ipset: fix hash:net,port,net hang with /0 subnet
netfilter: ipset: Rework long task execution when adding/deleting entries
include/linux/netfilter/ipset/ip_set.h | 2 +-
net/netfilter/ipset/ip_set_core.c | 7 ++---
net/netfilter/ipset/ip_set_hash_ip.c | 14 +++++-----
net/netfilter/ipset/ip_set_hash_ipmark.c | 13 ++++-----
net/netfilter/ipset/ip_set_hash_ipport.c | 13 ++++-----
net/netfilter/ipset/ip_set_hash_ipportip.c | 13 ++++-----
net/netfilter/ipset/ip_set_hash_ipportnet.c | 13 +++++----
net/netfilter/ipset/ip_set_hash_net.c | 17 +++++-------
net/netfilter/ipset/ip_set_hash_netiface.c | 15 +++++------
net/netfilter/ipset/ip_set_hash_netnet.c | 23 +++++-----------
net/netfilter/ipset/ip_set_hash_netport.c | 19 +++++--------
net/netfilter/ipset/ip_set_hash_netportnet.c | 40 +++++++++++++++-------------
12 files changed, 89 insertions(+), 100 deletions(-)
next reply other threads:[~2022-12-30 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 12:24 Jozsef Kadlecsik [this message]
2022-12-30 12:24 ` [PATCH 1/2] netfilter: ipset: fix hash:net,port,net hang with /0 subnet Jozsef Kadlecsik
2022-12-30 12:24 ` [PATCH 2/2] netfilter: ipset: Rework long task execution when adding/deleting entries Jozsef Kadlecsik
2022-12-30 12:42 ` [PATCH 0/2] ipset patches for nf Jozsef Kadlecsik
2023-01-02 14:12 ` Pablo Neira Ayuso
2023-01-02 14:13 ` Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2020-02-22 11:30 Jozsef Kadlecsik
2020-02-26 13:02 ` Pablo Neira Ayuso
2017-02-19 18:24 Jozsef Kadlecsik
2017-02-21 13:05 ` Pablo Neira Ayuso
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=20221230122438.1618153-1-kadlec@netfilter.org \
--to=kadlec@netfilter.org \
--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;
as well as URLs for NNTP newsgroup(s).