summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorVishwanath Pai <vpai@akamai.com>2022-09-28 14:26:50 -0400
committerJozsef Kadlecsik <kadlec@netfilter.org>2022-11-07 22:21:30 +0100
commitb9194d8cc41e8c0a028d98f2d2fb5d08552cf7f0 (patch)
tree6dd8126487e38e3a6ae41443ac74417378cb5abf /README
parent2d83c65cf3d22516ae5d5104c0d576b81f32a7f4 (diff)
netfilter: ipset: regression in ip_set_hash_ip.c
This patch introduced a regression: commit 48596a8ddc46 ("netfilter: ipset: Fix adding an IPv4 range containing more than 2^31 addresses") The variable e.ip is passed to adtfn() function which finally adds the ip address to the set. The patch above refactored the for loop and moved e.ip = htonl(ip) to the end of the for loop. What this means is that if the value of "ip" changes between the first assignement of e.ip and the forloop, then e.ip is pointing to a different ip address than "ip". Test case: $ ipset create jdtest_tmp hash:ip family inet hashsize 2048 maxelem 100000 $ ipset add jdtest_tmp 10.0.1.1/31 ipset v6.21.1: Element cannot be added to the set: it's already added The value of ip gets updated inside the "else if (tb[IPSET_ATTR_CIDR])" block but e.ip is still pointing to the old value. Reviewed-by: Joshua Hunt <johunt@akamai.com> Signed-off-by: Vishwanath Pai <vpai@akamai.com> Signed-off-by: Jozsef Kadlecsik <kadlec@netfilter.org>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions