From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH nft 4/4] segtree: add interval overlap detection for dynamic updates
Date: Sat, 23 Apr 2016 18:08:40 +0200 [thread overview]
Message-ID: <1461427720-4939-5-git-send-email-pablo@netfilter.org> (raw)
In-Reply-To: <1461427720-4939-1-git-send-email-pablo@netfilter.org>
Make sure the new intervals that we want to add are not overlapping with
any of the existing ones.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
src/segtree.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 52 insertions(+), 3 deletions(-)
diff --git a/src/segtree.c b/src/segtree.c
index 879264b..1d505a5 100644
--- a/src/segtree.c
+++ b/src/segtree.c
@@ -327,12 +327,61 @@ static unsigned int expr_to_intervals(const struct expr *set,
return n;
}
-static int set_to_segtree(struct list_head *msgs, struct expr *init,
- struct seg_tree *tree)
+/* This function checks for overlaps in two ways:
+ *
+ * 1) A new interval end intersects an existing interval.
+ * 2) New intervals that are larger than existing ones, that don't intersect
+ * at all, but that wrap the existing ones.
+ */
+static bool interval_overlap(const struct elementary_interval *e1,
+ const struct elementary_interval *e2)
+{
+ return (mpz_cmp(e1->left, e2->left) >= 0 &&
+ mpz_cmp(e1->left, e2->right) <= 0) ||
+ (mpz_cmp(e1->right, e2->left) >= 0 &&
+ mpz_cmp(e1->right, e2->right) <= 0) ||
+ (mpz_cmp(e1->left, e2->left) <= 0 &&
+ mpz_cmp(e1->right, e2->right) >= 0);
+}
+
+static int set_overlap(struct list_head *msgs, const struct set *set,
+ struct expr *init, unsigned int keylen)
+{
+ struct elementary_interval *new_intervals[init->size];
+ struct elementary_interval *intervals[set->init->size];
+ unsigned int n, m, i, j;
+
+ n = expr_to_intervals(init, keylen, new_intervals);
+ m = expr_to_intervals(set->init, keylen, intervals);
+
+ for (i = 0; i < n; i++) {
+ for (j = 0; j < m; j++) {
+ if (interval_overlap(new_intervals[i], intervals[j]))
+ return expr_error(msgs,
+ new_intervals[i]->expr,
+ "interval overlaps with an existing one");
+ }
+ }
+
+ return 0;
+}
+
+static int set_to_segtree(struct list_head *msgs, struct set *set,
+ struct expr *init, struct seg_tree *tree, bool add)
{
struct elementary_interval *intervals[init->size];
struct expr *i, *next;
unsigned int n;
+ int err;
+
+ /* We are updating an existing set with new elements, check if the new
+ * interval overlaps with any of the existing ones.
+ */
+ if (add && set->init != init) {
+ err = set_overlap(msgs, set, init, tree->keylen);
+ if (err < 0)
+ return err;
+ }
n = expr_to_intervals(init, tree->keylen, intervals);
@@ -491,7 +540,7 @@ int set_to_intervals(struct list_head *errs, struct set *set,
LIST_HEAD(list);
seg_tree_init(&tree, set, init);
- if (set_to_segtree(errs, init, &tree) < 0)
+ if (set_to_segtree(errs, set, init, &tree, add) < 0)
return -1;
segtree_linearize(&list, set, init, &tree, add);
--
2.1.4
next prev parent reply other threads:[~2016-04-23 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 16:08 [PATCH nft 0/4] Interval overlap detection for named sets Pablo Neira Ayuso
2016-04-23 16:08 ` [PATCH nft 1/4] segtree: set expr->len for prefix expression from interval_map_decompose() Pablo Neira Ayuso
2016-04-23 16:08 ` [PATCH nft 2/4] segtree: add expr_to_intervals() Pablo Neira Ayuso
2016-04-23 16:08 ` [PATCH nft 3/4] segtree: rename set expression set_to_segtree() Pablo Neira Ayuso
2016-04-23 16:08 ` Pablo Neira Ayuso [this message]
2016-04-25 10:38 ` [PATCH nft 0/4] Interval overlap detection for named sets Patrick McHardy
2016-04-25 11:57 ` Pablo Neira Ayuso
2016-04-25 16:59 ` Patrick McHardy
2016-04-25 21:32 ` Pablo Neira Ayuso
2016-04-25 21:49 ` Patrick McHardy
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=1461427720-4939-5-git-send-email-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.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).