netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 0/2]: nftables: segtree fixes
Date: Thu, 16 Jan 2014 16:21:50 +0000	[thread overview]
Message-ID: <1389889312-4055-1-git-send-email-kaber@trash.net> (raw)

These patches fix a couple of broken cases and improve readability
in interval decomposition.

- mark datatypes where representations as prefixes is preferrable to ranges,
  like IP addresses, and use that to decide whether to use prefix or range
  expressions if both are possible

- fix a couple of bugs wrt. unclosed intervals

I'm working on some further improvements and cleanups, but these are the
minimum we should put in for the upcoming release to make the output
both understandable and correct.

Signed-off-by: Patrick McHardy <kaber@trash.net>

             reply	other threads:[~2014-01-16 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 16:21 Patrick McHardy [this message]
2014-01-16 16:21 ` [PATCH 1/2] segtree: only use prefix expressions for ranges for selected datatypes Patrick McHardy
2014-01-16 16:21 ` [PATCH 2/2] segtree: fix decomposition of unclosed intervals 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=1389889312-4055-1-git-send-email-kaber@trash.net \
    --to=kaber@trash.net \
    --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).