netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: kaber@trash.net
Subject: [PATCH 0/6 nft] improvements for the range printing
Date: Tue,  2 Jun 2015 19:03:01 +0200	[thread overview]
Message-ID: <1433264587-29705-1-git-send-email-pablo@netfilter.org> (raw)

Hi Patrick,

This patchset adds the routine to consolidate the range printing from the
delinearization step, so we get:

        tcp dport 1024-65535

instead of:

        tcp dport >= 1024 tcp dport 65535

Same thing with meta and ct selectors.

This applies on top of the next-4.1 branch that I'll merge asap to master to
start preparing the next 0.5 release.

Let me know if you have any concern, thanks.

Pablo Neira Ayuso (6):
  netlink_delinearize: pass ctx pointer to stmt_reject_postprocess()
  netlink_delinearize: keep pointer to current statement from rule_pp_ctx
  netlink_delinearize: add payload_match_expand()
  netlink_delinearize: consolidate range printing
  tests: regression: reduce code duplication a bit on error reporting
  tests: regression: fix warnings related to range listing

 src/netlink_delinearize.c         |  218 +++++++++++++++++++++++++------------
 tests/regression/any/ct.t         |   26 ++---
 tests/regression/any/frag.t       |   10 +-
 tests/regression/any/meta.t       |   43 ++++----
 tests/regression/arp/arp.t        |   14 +--
 tests/regression/inet/ah.t        |   16 +--
 tests/regression/inet/comp.t      |    8 +-
 tests/regression/inet/dccp.t      |   11 +-
 tests/regression/inet/esp.t       |    8 +-
 tests/regression/inet/sctp.t      |   16 +--
 tests/regression/inet/tcp.t       |   30 ++---
 tests/regression/inet/udp.t       |   20 ++--
 tests/regression/inet/udplite.t   |   18 +--
 tests/regression/ip/icmp.t        |   20 ++--
 tests/regression/ip/ip.t          |   38 +++----
 tests/regression/ip/masquerade.t  |    2 +-
 tests/regression/ip/nat.t         |   14 +--
 tests/regression/ip/redirect.t    |    2 +-
 tests/regression/ip6/dst.t        |    8 +-
 tests/regression/ip6/hbh.t        |    8 +-
 tests/regression/ip6/ip6.t        |   12 +-
 tests/regression/ip6/masquerade.t |    2 +-
 tests/regression/ip6/mh.t         |   18 +--
 tests/regression/ip6/redirect.t   |    2 +-
 tests/regression/ip6/rt.t         |   16 +--
 tests/regression/nft-test.py      |   19 ++--
 26 files changed, 337 insertions(+), 262 deletions(-)

--
1.7.10.4


             reply	other threads:[~2015-06-02 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 17:03 Pablo Neira Ayuso [this message]
2015-06-02 17:03 ` [PATCH 1/6 nft] netlink_delinearize: pass ctx pointer to stmt_reject_postprocess() Pablo Neira Ayuso
2015-06-02 17:03 ` [PATCH 2/6 nft] netlink_delinearize: keep pointer to current statement from rule_pp_ctx Pablo Neira Ayuso
2015-06-02 17:03 ` [PATCH 3/6 nft] netlink_delinearize: add payload_match_expand() Pablo Neira Ayuso
2015-06-02 17:03 ` [PATCH 4/6 nft] netlink_delinearize: consolidate range printing Pablo Neira Ayuso
2015-06-02 17:03 ` [PATCH 5/6 nft] tests: regression: reduce code duplication a bit on error reporting Pablo Neira Ayuso
2015-06-02 17:03 ` [PATCH 6/6 nft] tests: regression: fix warnings related to range listing Pablo Neira Ayuso

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=1433264587-29705-1-git-send-email-pablo@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=kaber@trash.net \
    --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).