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 v2 0/2] monitor: Fix printing of range elements in named sets
Date: Mon, 17 Jul 2017 17:06:04 +0200 [thread overview]
Message-ID: <20170717150606.32097-1-phil@nwl.cc> (raw)
This is supposed to be v2 of my patch series sent earlier, but it turned
into a complete rewrite of the whole SETELEM callback and so there is no
reuse of former changes.
The second patch adds a simple testbench for 'nft monitor' output which
helped me quite a lot to get things right.
Phil Sutter (2):
monitor: Rewrite SETELEM callback
tests: Add basic monitor testing framework
src/netlink.c | 272 ++++++++++++++++++++++++++-------
tests/monitor/run-tests.sh | 78 ++++++++++
tests/monitor/testcases/set-mixed.t | 21 +++
tests/monitor/testcases/set-multiple.t | 15 ++
tests/monitor/testcases/set-simple.t | 49 ++++++
5 files changed, 382 insertions(+), 53 deletions(-)
create mode 100755 tests/monitor/run-tests.sh
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-17 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 15:06 Phil Sutter [this message]
2017-07-17 15:06 ` [nft PATCH 1/2] monitor: Rewrite SETELEM callback Phil Sutter
2017-07-17 16:30 ` Pablo Neira Ayuso
2017-07-17 16:41 ` Phil Sutter
2017-07-17 17:16 ` Pablo Neira Ayuso
2017-07-18 9:05 ` Phil Sutter
2017-07-18 9:09 ` Pablo Neira Ayuso
2017-07-18 9:17 ` Phil Sutter
2017-07-18 14:32 ` Pablo Neira Ayuso
2017-07-17 15:06 ` [nft PATCH 2/2] tests: Add basic monitor testing framework Phil Sutter
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=20170717150606.32097-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).