public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"alan.adamson@oracle.com" <alan.adamson@oracle.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: nvme in-band authentication blktests - nvme/043
Date: Mon, 3 Jul 2023 11:06:31 +0200	[thread overview]
Message-ID: <68c5be4d-3eed-cfc7-901a-59a9cd1bd4cd@suse.de> (raw)
In-Reply-To: <bu5hjttqtlxm4dqs2zfacsmrargz7kxpawkh2kfgitihlibk2a@356kctyedf6i>

On 7/3/23 08:46, Shinichiro Kawasaki wrote:
> CC+: Hannes,
> 
> On Jun 29, 2023 / 12:24, alan.adamson@oracle.com wrote:
>> I'm playing around with in-band authentication and using blktests to see how
>> to setup it up and use it.  In test nvme/043, a valid hostkey is never
>> initialized and a NULL is being used to setup the target and to connect.  Is
>> this expected?  The test with the NULL hostkey passes.  I updated the test
>> to use a valid key and it also passes.
>>
>>
>> diff --git a/tests/nvme/043 b/tests/nvme/043
>> index a030884..d5e0d4b 100755
>> --- a/tests/nvme/043
>> +++ b/tests/nvme/043
>> @@ -40,6 +40,8 @@ test() {
>>          fi
>>          hostnqn="nqn.2014-08.org.nvmexpress:uuid:${hostid}"
>>
>> +       hostkey="$(nvme gen-dhchap-key -n ${subsys_name} 2> /dev/null)"
>> +
>>          _setup_nvmet
>>
>>          truncate -s "${nvme_img_size}" "${file_path}"
>>
> 
> Alan's question looks valid for me.
> 
> Hannes, may I ask your comment?

Yeah, that's correct.

Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes



      reply	other threads:[~2023-07-03  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 19:24 nvme in-band authentication blktests - nvme/043 alan.adamson
2023-07-03  6:46 ` Shinichiro Kawasaki
2023-07-03  9:06   ` Hannes Reinecke [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=68c5be4d-3eed-cfc7-901a-59a9cd1bd4cd@suse.de \
    --to=hare@suse.de \
    --cc=alan.adamson@oracle.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=shinichiro.kawasaki@wdc.com \
    /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