From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] nvme: add re-authentication running concurrently with reset
Date: Tue, 15 Nov 2022 09:39:06 +0000 [thread overview]
Message-ID: <20221115093904.kdgemo7w5fk2bu7w@shindev> (raw)
In-Reply-To: <20221114125252.1086763-1-sagi@grimberg.me>
On Nov 14, 2022 / 14:52, Sagi Grimberg wrote:
> when re-authentication with new host-key and/or ctrl-key there is an
> async work that is scheduled async. A controller reset should be mutual
> exclusive with the re-authentication work. Add a test that triggers
> re-authentication and immediately resets the controller.
>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Thanks. I believe that this test case checks fix of a problem found during your
work on "nvme: fixes, cleanups and enhancements to the dhchap-auth host code".
I have some nit comments. Other than these, the patch looks good for me.
- Shellcheck have a couple of complaints:
$ make check
shellcheck -x -e SC2119 -f gcc check new common/* \
tests/*/rc tests/*/[0-9]*[0-9]
tests/nvme/046:87:20: note: Double quote to prevent globbing and word splitting. [SC2086]
tests/nvme/046:93:20: note: Double quote to prevent globbing and word splitting. [SC2086]
make: *** [Makefile:21: check] Error 1
- The test() function lists all local variables except "hostkey_file",
"ctrlkey_file" and "nvvmedev". A bit better to declare those three also.
- It would be a bit better for linux-nvme readers to have subject prefix
"[PATCH blktests]" to clarify it is not the patch for linux, but for blktests.
--
Shin'ichiro Kawasaki
prev parent reply other threads:[~2022-11-15 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 12:52 [PATCH] nvme: add re-authentication running concurrently with reset Sagi Grimberg
2022-11-14 19:03 ` Chaitanya Kulkarni
2022-11-15 9:39 ` Shinichiro Kawasaki [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=20221115093904.kdgemo7w5fk2bu7w@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--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