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: [PATCH blktests 0/6] Testsuite for nvme in-band authentication
Date: Fri, 12 Nov 2021 15:45:04 +0100 [thread overview]
Message-ID: <20211112144510.98523-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.
Hannes Reinecke (6):
nvmeof-tcp/001: simple test for nvmeof-tcp connection
nvmeof-tcp/002: create an authenticated nvmeof-tcp connection
nvmeof-tcp/003: test different key types
nvmeof-tcp/004: test hash and dhgroup variations
nvmeof-tcp/005: test bi-directional authentication
nvmeof-tcp/006: test re-authentication
tests/nvmeof-tcp/001 | 55 +++++++
tests/nvmeof-tcp/001.out | 6 +
tests/nvmeof-tcp/002 | 62 +++++++
tests/nvmeof-tcp/002.out | 6 +
tests/nvmeof-tcp/003 | 100 +++++++++++
tests/nvmeof-tcp/003.out | 36 ++++
tests/nvmeof-tcp/004 | 86 ++++++++++
tests/nvmeof-tcp/004.out | 37 +++++
tests/nvmeof-tcp/005 | 74 +++++++++
tests/nvmeof-tcp/005.out | 6 +
tests/nvmeof-tcp/006 | 113 +++++++++++++
tests/nvmeof-tcp/006.out | 23 +++
tests/nvmeof-tcp/rc | 347 +++++++++++++++++++++++++++++++++++++++
13 files changed, 951 insertions(+)
create mode 100644 tests/nvmeof-tcp/001
create mode 100644 tests/nvmeof-tcp/001.out
create mode 100644 tests/nvmeof-tcp/002
create mode 100644 tests/nvmeof-tcp/002.out
create mode 100644 tests/nvmeof-tcp/003
create mode 100644 tests/nvmeof-tcp/003.out
create mode 100644 tests/nvmeof-tcp/004
create mode 100644 tests/nvmeof-tcp/004.out
create mode 100644 tests/nvmeof-tcp/005
create mode 100644 tests/nvmeof-tcp/005.out
create mode 100644 tests/nvmeof-tcp/006
create mode 100644 tests/nvmeof-tcp/006.out
create mode 100644 tests/nvmeof-tcp/rc
--
2.26.2
next reply other threads:[~2021-11-12 15:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 14:45 Hannes Reinecke [this message]
2021-11-12 14:45 ` [PATCH 1/6] nvmeof-tcp/001: simple test for nvmeof-tcp connection Hannes Reinecke
2021-11-14 10:31 ` Sagi Grimberg
2021-11-14 13:50 ` Hannes Reinecke
2021-11-14 14:45 ` Sagi Grimberg
2021-11-15 2:34 ` Chaitanya Kulkarni
2021-11-15 6:56 ` Hannes Reinecke
2021-11-15 8:12 ` Sagi Grimberg
2021-11-15 8:37 ` Hannes Reinecke
2021-11-12 14:45 ` [PATCH 2/6] nvmeof-tcp/002: create an authenticated " Hannes Reinecke
2021-11-12 14:45 ` [PATCH 3/6] nvmeof-tcp/003: test different key types Hannes Reinecke
2021-11-12 14:45 ` [PATCH 4/6] nvmeof-tcp/004: test hash and dhgroup variations Hannes Reinecke
2021-11-12 14:45 ` [PATCH 5/6] nvmeof-tcp/005: test bi-directional authentication Hannes Reinecke
2021-11-17 21:50 ` Sagi Grimberg
2021-11-18 9:40 ` Hannes Reinecke
2021-11-19 11:29 ` Hannes Reinecke
2021-11-12 14:45 ` [PATCH 6/6] nvmeof-tcp/006: test re-authentication 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=20211112144510.98523-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