From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nft 0/5] tests: shell: add and use feature probing
Date: Mon, 4 Sep 2023 11:06:29 +0200 [thread overview]
Message-ID: <20230904090640.3015-1-fw@strlen.de> (raw)
This series allows to run run-tests.sh on the centos-stream-9 kernel,
which is based on 5.14.y, with all tests either passing or getting
skipped as the feature tested isn't available.
Before:
I: results: [OK] 366 [FAILED] 7 [TOTAL] 373
After:
I: results: [OK] 370 [FAILED] 0 [SKIPPED] 3 [TOTAL] 373
First patch adds feature probe skeleton, second patch adds feature
probe for netdev chains without a device.
Third patch alters a few test cases to no longer depend on 'inner header
offset base'.
Patch 4 adds and uses feature probe test for treating maps like sets
and last patch does the same for the inner header base offset.
Florian Westphal (5):
tests: add feature probing
tests: shell: let netdev_chain_0 test indicate SKIP if kernel requires
netdev device
tests: shell: typeof_integer/raw: prefer @nh for payload matching
tests: shell: add and use feature probe for map query like a set
tests: shell skip inner matching tests if unsupported
tests/shell/features/chain_binding.nft | 7 +++
tests/shell/features/inner_matching.nft | 7 +++
tests/shell/features/map_lookup.nft | 11 ++++
.../features/netdev_chain_without_device.nft | 7 +++
tests/shell/run-tests.sh | 35 ++++++++++++-
tests/shell/testcases/chains/netdev_chain_0 | 2 +
.../testcases/maps/dumps/typeof_integer_0.nft | 4 +-
.../testcases/maps/dumps/typeof_raw_0.nft | 4 +-
tests/shell/testcases/maps/typeof_integer_0 | 4 +-
.../testcases/maps/typeof_maps_add_delete | 35 ++++++++++---
tests/shell/testcases/maps/typeof_raw_0 | 4 +-
.../testcases/sets/dumps/typeof_raw_0.nft | 4 +-
tests/shell/testcases/sets/inner_0 | 2 +
tests/shell/testcases/sets/typeof_raw_0 | 4 +-
tests/shell/testcases/transactions/30s-stress | 52 ++++++++++++++++---
15 files changed, 154 insertions(+), 28 deletions(-)
create mode 100644 tests/shell/features/chain_binding.nft
create mode 100644 tests/shell/features/inner_matching.nft
create mode 100644 tests/shell/features/map_lookup.nft
create mode 100644 tests/shell/features/netdev_chain_without_device.nft
--
2.41.0
next reply other threads:[~2023-09-04 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 9:06 Florian Westphal [this message]
2023-09-04 9:06 ` [PATCH nft 1/5] tests: add feature probing Florian Westphal
2023-09-05 13:00 ` Phil Sutter
2023-09-05 13:44 ` Florian Westphal
2023-09-05 14:01 ` Phil Sutter
2023-09-05 14:09 ` Florian Westphal
2023-09-05 20:28 ` Phil Sutter
2023-09-06 5:17 ` Thomas Haller
2023-09-06 14:36 ` Thomas Haller
2023-09-04 9:06 ` [PATCH nft 2/5] tests: shell: let netdev_chain_0 test indicate SKIP if kernel requires netdev device Florian Westphal
2023-09-05 13:03 ` Phil Sutter
2023-09-06 13:42 ` Thomas Haller
2023-09-04 9:06 ` [PATCH nft 3/5] tests: shell: typeof_integer/raw: prefer @nh for payload matching Florian Westphal
2023-09-04 9:06 ` [PATCH nft 4/5] tests: shell: add and use feature probe for map query like a set Florian Westphal
2023-09-06 14:39 ` Thomas Haller
2023-09-04 9:06 ` [PATCH nft 5/5] tests: shell skip inner matching tests if unsupported Florian Westphal
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=20230904090640.3015-1-fw@strlen.de \
--to=fw@strlen.de \
--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).