From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [nft PATCH 0/9] Testsuite-indicated fixes for JSON
Date: Thu, 9 May 2019 13:35:36 +0200 [thread overview]
Message-ID: <20190509113545.4017-1-phil@nwl.cc> (raw)
Running tests/py/nft-test.py with -j flag and trying to eliminate
errors/warnings resulted in the following series of fixes. They are
about half and half changes to code and test cases.
Phil Sutter (9):
json: Support nat in inet family
parser_json: Fix igmp support
netlink: Fix printing of zero-length prefixes
tests/py: Fix JSON equivalents of osf tests
json: Fix tproxy support regarding latest changes
parser_json: Fix ct timeout object support
tests/py: Fix for ip dscp symbol "le"
tests/py: Fix JSON expexted output after expr merge change
tests/py: Fix JSON expected output for icmpv6 code values
doc/libnftables-json.adoc | 5 +
src/json.c | 31 +--
src/netlink_delinearize.c | 4 +-
src/parser_json.c | 26 ++-
tests/py/inet/dnat.t.json | 166 +++++++++++++++
tests/py/inet/osf.t.json | 59 +++++-
tests/py/inet/snat.t.json | 131 ++++++++++++
tests/py/inet/tcp.t.json.output | 44 +---
tests/py/inet/tproxy.t | 2 +-
tests/py/inet/tproxy.t.json | 80 ++++++++
tests/py/inet/tproxy.t.payload | 2 +-
tests/py/ip/igmp.t.json | 323 ++++++++++++++++++++++++++++++
tests/py/ip/ip.t | 2 +-
tests/py/ip/ip.t.json | 2 +-
tests/py/ip/ip.t.payload | 4 +-
tests/py/ip/tproxy.t | 2 +-
tests/py/ip/tproxy.t.json | 26 ++-
tests/py/ip/tproxy.t.json.output | 61 ++++++
tests/py/ip6/icmpv6.t.json.output | 59 ++++++
tests/py/ip6/ip6.t | 2 +-
tests/py/ip6/ip6.t.json | 2 +-
tests/py/ip6/ip6.t.payload.inet | 4 +-
tests/py/ip6/ip6.t.payload.ip6 | 4 +-
tests/py/ip6/tproxy.t | 2 +-
tests/py/ip6/tproxy.t.json | 26 ++-
tests/py/ip6/tproxy.t.json.output | 60 ++++++
26 files changed, 1041 insertions(+), 88 deletions(-)
create mode 100644 tests/py/inet/dnat.t.json
create mode 100644 tests/py/inet/snat.t.json
create mode 100644 tests/py/ip/igmp.t.json
create mode 100644 tests/py/ip/tproxy.t.json.output
create mode 100644 tests/py/ip6/tproxy.t.json.output
--
2.21.0
next reply other threads:[~2019-05-09 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 11:35 Phil Sutter [this message]
2019-05-09 11:35 ` [nft PATCH 1/9] json: Support nat in inet family Phil Sutter
2019-05-09 11:35 ` [nft PATCH 2/9] parser_json: Fix igmp support Phil Sutter
2019-05-09 11:35 ` [nft PATCH 3/9] netlink: Fix printing of zero-length prefixes Phil Sutter
2019-05-09 11:35 ` [nft PATCH 4/9] tests/py: Fix JSON equivalents of osf tests Phil Sutter
2019-05-09 11:35 ` [nft PATCH 5/9] json: Fix tproxy support regarding latest changes Phil Sutter
2019-05-09 11:35 ` [nft PATCH 6/9] parser_json: Fix ct timeout object support Phil Sutter
2019-05-09 11:35 ` [nft PATCH 7/9] tests/py: Fix for ip dscp symbol "le" Phil Sutter
2019-05-09 15:11 ` Pablo Neira Ayuso
2019-05-09 15:11 ` Pablo Neira Ayuso
2019-05-09 15:37 ` Phil Sutter
2019-05-09 11:35 ` [nft PATCH 8/9] tests/py: Fix JSON expexted output after expr merge change Phil Sutter
2019-05-09 11:35 ` [nft PATCH 9/9] tests/py: Fix JSON expected output for icmpv6 code values Phil Sutter
2019-05-09 15:00 ` [nft PATCH 0/9] Testsuite-indicated fixes for JSON 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=20190509113545.4017-1-phil@nwl.cc \
--to=phil@nwl.cc \
--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).