From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH blktests] nvme: add dh module requirement for tests that involve dh groups
Date: Tue, 30 Aug 2022 04:46:33 +0000 [thread overview]
Message-ID: <20220830044632.j7k45lhdlyvksrxh@shindev> (raw)
In-Reply-To: <20220829083614.874878-1-sagi@grimberg.me>
Hi Sagi,
On Aug 29, 2022 / 11:36, Sagi Grimberg wrote:
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> tests/nvme/043 | 1 +
> tests/nvme/044 | 1 +
> tests/nvme/045 | 1 +
> 3 files changed, 3 insertions(+)
>
> diff --git a/tests/nvme/043 b/tests/nvme/043
> index 381ae755f140..87273e5b414d 100755
> --- a/tests/nvme/043
> +++ b/tests/nvme/043
> @@ -16,6 +16,7 @@ requires() {
> _have_kernel_option NVME_TARGET_AUTH
> _require_nvme_trtype_is_fabrics
> _require_nvme_cli_auth
> + _have_driver dh_generic
> }
Do you see failure without this check? As far as I understand, this new check is
equivalent to '_have_kernel_option CRYPTO_DH'. This test case already requires
'_have_kernel_option NVME_AUTH' and CONFIG_NVME_AUTH selects CONFIG_CRYPTO_DH.
So, the new check does not look required assuming dh_generic.ko is built and
installed correctly.
>
>
> diff --git a/tests/nvme/044 b/tests/nvme/044
> index 046553198ce3..13019659b951 100755
> --- a/tests/nvme/044
> +++ b/tests/nvme/044
> @@ -16,6 +16,7 @@ requires() {
> _have_kernel_option NVME_TARGET_AUTH
> _require_nvme_trtype_is_fabrics
> _require_nvme_cli_auth
> + _have_driver dh_generic
> }
>
>
> diff --git a/tests/nvme/045 b/tests/nvme/045
> index b60f18fc9f87..264f21053921 100755
> --- a/tests/nvme/045
> +++ b/tests/nvme/045
> @@ -16,6 +16,7 @@ requires() {
> _have_kernel_option NVME_TARGET_AUTH
> _require_nvme_trtype_is_fabrics
> _require_nvme_cli_auth
> + _have_driver dh_generic
> }
>
>
> --
> 2.34.1
>
--
Shin'ichiro Kawasaki
next prev parent reply other threads:[~2022-08-30 4:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 8:36 [PATCH blktests] nvme: add dh module requirement for tests that involve dh groups Sagi Grimberg
2022-08-30 4:46 ` Shinichiro Kawasaki [this message]
2022-08-30 7:05 ` Sagi Grimberg
2022-08-30 7:13 ` Jackie Liu
2022-08-30 7:37 ` Sagi Grimberg
2022-08-30 7:44 ` Jackie Liu
2022-08-30 10:23 ` Shinichiro Kawasaki
2022-08-30 13:26 ` Sagi Grimberg
2022-08-31 4:59 ` Shinichiro Kawasaki
2022-09-09 4:14 ` Shinichiro Kawasaki
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=20220830044632.j7k45lhdlyvksrxh@shindev \
--to=shinichiro.kawasaki@wdc.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--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