netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Haller <thaller@redhat.com>
To: NetFilter <netfilter-devel@vger.kernel.org>
Cc: Thomas Haller <thaller@redhat.com>
Subject: [PATCH nft v2 4/4] tests/shell: add ".nft" dump files for tests without dumps/ directory
Date: Fri,  8 Sep 2023 16:14:27 +0200	[thread overview]
Message-ID: <20230908141634.1023071-5-thaller@redhat.com> (raw)
In-Reply-To: <20230908141634.1023071-1-thaller@redhat.com>

DUMPGEN=y mode skips tests that don't have a corresponding "dumps/"
directory.

Add the "dumps/" directory for tests that lacked it, and generate ".nft"
files by running `./tests/shell/run-tests.sh -g`.

Yes, they are all empty. Not very exciting, but why not check for that
too?

Signed-off-by: Thomas Haller <thaller@redhat.com>
---
 tests/shell/testcases/bogons/dumps/assert_failures.nft    | 0
 tests/shell/testcases/netns/dumps/0001nft-f_0.nft         | 0
 tests/shell/testcases/netns/dumps/0002loosecommands_0.nft | 0
 tests/shell/testcases/netns/dumps/0003many_0.nft          | 0
 tests/shell/testcases/nft-i/dumps/0001define_0.nft        | 0
 tests/shell/testcases/owner/dumps/0001-flowtable-uaf.nft  | 0
 6 files changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 tests/shell/testcases/bogons/dumps/assert_failures.nft
 create mode 100644 tests/shell/testcases/netns/dumps/0001nft-f_0.nft
 create mode 100644 tests/shell/testcases/netns/dumps/0002loosecommands_0.nft
 create mode 100644 tests/shell/testcases/netns/dumps/0003many_0.nft
 create mode 100644 tests/shell/testcases/nft-i/dumps/0001define_0.nft
 create mode 100644 tests/shell/testcases/owner/dumps/0001-flowtable-uaf.nft

diff --git a/tests/shell/testcases/bogons/dumps/assert_failures.nft b/tests/shell/testcases/bogons/dumps/assert_failures.nft
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/tests/shell/testcases/netns/dumps/0001nft-f_0.nft b/tests/shell/testcases/netns/dumps/0001nft-f_0.nft
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/tests/shell/testcases/netns/dumps/0002loosecommands_0.nft b/tests/shell/testcases/netns/dumps/0002loosecommands_0.nft
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/tests/shell/testcases/netns/dumps/0003many_0.nft b/tests/shell/testcases/netns/dumps/0003many_0.nft
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/tests/shell/testcases/nft-i/dumps/0001define_0.nft b/tests/shell/testcases/nft-i/dumps/0001define_0.nft
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/tests/shell/testcases/owner/dumps/0001-flowtable-uaf.nft b/tests/shell/testcases/owner/dumps/0001-flowtable-uaf.nft
new file mode 100644
index 000000000000..e69de29bb2d1
-- 
2.41.0


      parent reply	other threads:[~2023-09-08 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 14:14 [PATCH nft v2 0/4] tests/shell: add missing .nft and .nodump files Thomas Haller
2023-09-08 14:14 ` [PATCH nft v2 1/4] tests/shell: honor .nodump file for tests without nft dumps Thomas Haller
2023-09-08 14:14 ` [PATCH nft v2 2/4] tests/shell: generate and add ".nft" dump files for existing tests Thomas Haller
2023-09-08 14:14 ` [PATCH nft v2 3/4] tests/shell: add missing ".nodump" file for tests without dumps Thomas Haller
2023-09-08 14:14 ` Thomas Haller [this message]

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=20230908141634.1023071-5-thaller@redhat.com \
    --to=thaller@redhat.com \
    --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).