From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org,
Arturo Borrero Gonzalez <arturo@netfilter.org>
Subject: [nft PATCH v4 0/3] Fix printing of range elements in named sets
Date: Wed, 19 Jul 2017 15:05:26 +0200 [thread overview]
Message-ID: <20170719130529.25398-1-phil@nwl.cc> (raw)
This is v4 of 'nft monitor' fixes for range elements. Apart from
changing the new flag's location in struct expr as requested, this
series now also covers mappings.
Arturo Borrero Gonzalez (1):
monitor: Fix printing of range elements in named sets
Phil Sutter (2):
segtree: Introduce flag for half-open range elements
tests: Add basic monitor testing framework
include/expression.h | 1 +
include/rule.h | 18 +++++
src/netlink.c | 123 +++++++++++++++++++++++++++------
src/segtree.c | 5 ++
tests/monitor/run-tests.sh | 78 +++++++++++++++++++++
tests/monitor/testcases/set-maps.t | 11 +++
tests/monitor/testcases/set-mixed.t | 19 +++++
tests/monitor/testcases/set-multiple.t | 13 ++++
tests/monitor/testcases/set-simple.t | 47 +++++++++++++
9 files changed, 294 insertions(+), 21 deletions(-)
create mode 100755 tests/monitor/run-tests.sh
create mode 100644 tests/monitor/testcases/set-maps.t
create mode 100644 tests/monitor/testcases/set-mixed.t
create mode 100644 tests/monitor/testcases/set-multiple.t
create mode 100644 tests/monitor/testcases/set-simple.t
--
2.13.1
next reply other threads:[~2017-07-19 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 13:05 Phil Sutter [this message]
2017-07-19 13:05 ` [nft PATCH v2 1/3] segtree: Introduce flag for half-open range elements Phil Sutter
2017-07-19 13:05 ` [nft PATCH v3 2/3] monitor: Fix printing of range elements in named sets Phil Sutter
2017-07-19 17:17 ` Pablo Neira Ayuso
2017-07-19 18:22 ` Phil Sutter
2017-07-19 13:05 ` [nft PATCH v2 3/3] tests: Add basic monitor testing framework Phil Sutter
2017-07-19 17:16 ` [nft PATCH v4 0/3] Fix printing of range elements in named sets 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=20170719130529.25398-1-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=arturo@netfilter.org \
--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).