From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <keith.busch@wdc.com>,
Omar Sandoval <osandov@fb.com>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCHv2 blktests 0/9] Testsuite for nvme in-band authentication
Date: Mon, 22 Nov 2021 08:55:15 +0100 [thread overview]
Message-ID: <20211122075524.26207-1-hare@suse.de> (raw)
Hi all,
some people (Hi Sagi!) have complained that nvme in-band authentication
provide far too many configuration options to test it with some easy
commands. So here's a test suite for testing (most of) the various
configuration options and features.
As usual, comments and reviews are welcome.
Changes to v1:
- Move tests to the 'nvme' directory
- Check for authentication failure on invalid keys
Hannes Reinecke (9):
nvme/rc: do not print error message when no nvme device is found
nvme/rc: clear allowed_hosts subdirectory
nvme/rc: add functions for in-band authentication
nvme/039: simple test for nvmeof-tcp connection
nvme/040: create an authenticated nvmeof-tcp connection
nvme/041: test different key types
nvme/042: test hash and dhgroup variations
nvme/043: test bi-directional authentication
nvme/044: test re-authentication
tests/nvme/039 | 56 ++++++++++++++++++++++
tests/nvme/039.out | 6 +++
tests/nvme/040 | 64 +++++++++++++++++++++++++
tests/nvme/040.out | 6 +++
tests/nvme/041 | 102 +++++++++++++++++++++++++++++++++++++++
tests/nvme/041.out | 36 ++++++++++++++
tests/nvme/042 | 88 ++++++++++++++++++++++++++++++++++
tests/nvme/042.out | 37 +++++++++++++++
tests/nvme/043 | 104 ++++++++++++++++++++++++++++++++++++++++
tests/nvme/043.out | 14 ++++++
tests/nvme/044 | 116 +++++++++++++++++++++++++++++++++++++++++++++
tests/nvme/044.out | 22 +++++++++
tests/nvme/rc | 56 ++++++++++++++++++++++
13 files changed, 707 insertions(+)
create mode 100644 tests/nvme/039
create mode 100644 tests/nvme/039.out
create mode 100644 tests/nvme/040
create mode 100644 tests/nvme/040.out
create mode 100644 tests/nvme/041
create mode 100644 tests/nvme/041.out
create mode 100644 tests/nvme/042
create mode 100644 tests/nvme/042.out
create mode 100644 tests/nvme/043
create mode 100644 tests/nvme/043.out
create mode 100644 tests/nvme/044
create mode 100644 tests/nvme/044.out
--
2.26.2
next reply other threads:[~2021-11-22 8:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 7:55 Hannes Reinecke [this message]
2021-11-22 7:55 ` [PATCH 1/9] nvme/rc: do not print error message when no nvme device is found Hannes Reinecke
2021-11-22 8:49 ` Sagi Grimberg
2021-11-22 7:55 ` [PATCH 2/9] nvme/rc: clear allowed_hosts subdirectory Hannes Reinecke
2021-11-22 8:49 ` Sagi Grimberg
2021-11-22 7:55 ` [PATCH 3/9] nvme/rc: add functions for in-band authentication Hannes Reinecke
2021-11-22 8:52 ` Sagi Grimberg
2021-11-22 9:24 ` Hannes Reinecke
2021-11-22 7:55 ` [PATCH 4/9] nvme/039: simple test for nvmeof-tcp connection Hannes Reinecke
2021-11-22 8:52 ` Sagi Grimberg
2021-11-22 9:18 ` Hannes Reinecke
2021-11-22 9:40 ` Sagi Grimberg
2021-11-22 9:41 ` Hannes Reinecke
2021-11-22 7:55 ` [PATCH 5/9] nvme/040: create an authenticated " Hannes Reinecke
2021-11-22 8:57 ` Sagi Grimberg
2021-11-22 9:22 ` Hannes Reinecke
2021-11-22 9:44 ` Sagi Grimberg
2021-11-22 7:55 ` [PATCH 6/9] nvme/041: test different key types Hannes Reinecke
2021-11-22 8:58 ` Sagi Grimberg
2021-11-22 9:25 ` Hannes Reinecke
2021-11-22 9:45 ` Sagi Grimberg
2021-11-22 7:55 ` [PATCH 7/9] nvme/042: test hash and dhgroup variations Hannes Reinecke
2021-11-22 7:55 ` [PATCH 8/9] nvme/043: test bi-directional authentication Hannes Reinecke
2021-11-22 7:55 ` [PATCH 9/9] nvme/044: test re-authentication Hannes Reinecke
2021-11-22 9:02 ` Sagi Grimberg
2021-11-22 9:40 ` Hannes Reinecke
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=20211122075524.26207-1-hare@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=keith.busch@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--cc=osandov@fb.com \
--cc=sagi@grimberg.me \
/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