From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [PATCH 0/1] ipset patch for the nf tree
Date: Tue, 22 Nov 2022 20:18:57 +0100 [thread overview]
Message-ID: <20221122191858.1051777-1-kadlec@netfilter.org> (raw)
Hi Pablo,
Please apply the next one-liner patch to your nf tree. Thanks!
- The "netfilter: ipset: enforce documented limit to prevent allocating
huge memory" patch contained a wrong condition which makes impossible to
add up to 64 clashing elements to a hash:net,iface type of set while it is
the documented feature of the set type. The patch fixes the condition and
thus makes possible to add the elements while keeps preventing allocating
huge memory.
Best regards,
Jozsef
The following changes since commit c7aa1a76d4a0a3c401025b60c401412bbb60f8c6:
netfilter: ipset: regression in ip_set_hash_ip.c (2022-11-21 15:00:45 +0100)
are available in the Git repository at:
git://blackhole.kfki.hu/nf 5e8cc0ff84d763559
for you to fetch changes up to 5e8cc0ff84d763559d34e3ddf5a1e645712ead54:
netfilter: ipset: restore allowing 64 clashing elements in hash:net,iface (2022-11-22 20:07:27 +0100)
----------------------------------------------------------------
Jozsef Kadlecsik (1):
netfilter: ipset: restore allowing 64 clashing elements in hash:net,iface
net/netfilter/ipset/ip_set_hash_gen.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2022-11-22 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 19:18 Jozsef Kadlecsik [this message]
2022-11-22 19:18 ` [PATCH 1/1] netfilter: ipset: restore allowing 64 clashing elements in hash:net,iface Jozsef Kadlecsik
2022-11-22 20:45 ` Pablo Neira Ayuso
2022-11-22 22:13 ` Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2021-07-27 11:17 [PATCH 0/1] ipset patch for the nf tree Jozsef Kadlecsik
2018-01-12 10:16 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=20221122191858.1051777-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.