summaryrefslogtreecommitdiffstats
path: root/src
diff options
context:
space:
mode:
authorPablo Neira Ayuso <pablo@netfilter.org>2022-06-13 17:22:47 +0200
committerPablo Neira Ayuso <pablo@netfilter.org>2022-06-19 00:55:20 +0200
commit87ba510fc704f766b5417d3bfc326e8ab9378c2a (patch)
tree7da24c5ceb33a8a76168a5e2b9e4715bb8976922 /src
parent498a5f0c219d8a118af4f172f248647d9b077101 (diff)
intervals: do not report exact overlaps for new elements
Two new elements that represent an exact overlap should not trigger an error. add table t add set t s { type ipv4_addr; flags interval; } add element t s { 1.0.1.0/24 } ... add element t s { 1.0.1.0/24 } result in a bogus error. # nft -f set.nft set.nft:1002:19-28: Error: conflicting intervals specified add element t s { 1.0.1.0/24 } ^^^^^^^^^^ Fixes: 3da9643fb9ff ("intervals: add support to automerge with kernel elements") Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'src')
-rw-r--r--src/intervals.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/intervals.c b/src/intervals.c
index bc414d6c..89f5c33d 100644
--- a/src/intervals.c
+++ b/src/intervals.c
@@ -540,8 +540,7 @@ static int setelem_overlap(struct list_head *msgs, struct set *set,
}
if (mpz_cmp(prev_range.low, range.low) == 0 &&
- mpz_cmp(prev_range.high, range.high) == 0 &&
- (elem->flags & EXPR_F_KERNEL || prev->flags & EXPR_F_KERNEL))
+ mpz_cmp(prev_range.high, range.high) == 0)
goto next;
if (mpz_cmp(prev_range.low, range.low) <= 0 &&