From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCHv14 00/11] nvme: In-band authentication support
Date: Fri, 10 Jun 2022 08:55:30 +0000 [thread overview]
Message-ID: <7b9bdd9a-1411-ca0d-9f87-71e2c25dffbb@nvidia.com> (raw)
In-Reply-To: <3d2cd533-6bd8-abfa-4df9-40aa6a2eae63@suse.de>
>>
>> blktests (master) # ./check nvme/039
>> nvme/039 (Create authenticated connections) [failed]
>> runtime 1.400s ... 1.707s
>> --- tests/nvme/039.out 2022-06-08 18:09:06.239931529 -0700
>> +++ /mnt/data/blktests/results/nodev/nvme/039.out.bad 2022-06-08
>> 18:09:40.596663692 -0700
>> @@ -1,6 +1,7 @@
>> Running nvme/039
>> +tests/nvme/rc: line 269: printf: write error: Invalid argument
>> Test unauthenticated connection
>> -no controller found
>> +no controller found: failed to write to nvme-fabrics device
>> NQN:blktests-subsystem-1 disconnected 0 controller(s)
>> Test authenticated connection
>> ...
>> (Run 'diff -u tests/nvme/039.out >
>> /mnt/data/blktests/results/nodev/nvme/039.out.bad' to see the entire
> diff)
>
> Hmm. Not sure what has happened here, but all blktests worked on my
> testbed. I'll be rechecking with the latest nvme-cli build.
>
> Which nvme-cli version did you use?
>
~ # nvme --version
nvme version 2.0 (git 2.0-96-g0b286b1)
libnvme version 1.0 (git 1.0-62-gaacaeea)
~ #
I'm I using wrong version ?
Can we please add check in the blktests to skip the test
if we have wrong wrong nvme-cli version ? it will help
others to not misdiagnosed the problem...
> Cheers,
>
> Hannes
-ck
next prev parent reply other threads:[~2022-06-10 8:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 14:45 [PATCHv14 00/11] nvme: In-band authentication support Hannes Reinecke
2022-06-08 14:45 ` [PATCH 01/11] crypto: add crypto_has_shash() Hannes Reinecke
2022-06-08 14:45 ` [PATCH 02/11] crypto: add crypto_has_kpp() Hannes Reinecke
2022-06-08 14:45 ` [PATCH 03/11] lib/base64: RFC4648-compliant base64 encoding Hannes Reinecke
2022-06-08 14:45 ` [PATCH 04/11] nvme: add definitions for NVMe In-Band authentication Hannes Reinecke
2022-06-08 14:45 ` [PATCH 05/11] nvme-fabrics: decode 'authentication required' connect error Hannes Reinecke
2022-06-08 14:45 ` [PATCH 06/11] nvme: Implement In-Band authentication Hannes Reinecke
2022-06-13 18:12 ` Christoph Hellwig
2022-06-20 6:50 ` Hannes Reinecke
2022-06-08 14:45 ` [PATCH 07/11] nvme-auth: Diffie-Hellman key exchange support Hannes Reinecke
2022-06-08 14:45 ` [PATCH 08/11] nvmet: parse fabrics commands on io queues Hannes Reinecke
2022-06-08 14:45 ` [PATCH 09/11] nvmet: Implement basic In-Band Authentication Hannes Reinecke
2022-06-08 14:45 ` [PATCH 10/11] nvmet-auth: Diffie-Hellman key exchange support Hannes Reinecke
2022-06-08 14:45 ` [PATCH 11/11] nvmet-auth: expire authentication sessions Hannes Reinecke
2022-06-09 1:13 ` [PATCHv14 00/11] nvme: In-band authentication support Chaitanya Kulkarni
2022-06-09 6:08 ` Hannes Reinecke
2022-06-09 6:20 ` Hannes Reinecke
2022-06-10 9:06 ` Chaitanya Kulkarni
2022-06-10 9:17 ` Chaitanya Kulkarni
2022-06-10 9:23 ` Hannes Reinecke
2022-06-10 8:55 ` Chaitanya Kulkarni [this message]
2022-06-10 9:12 ` Hannes Reinecke
2022-06-10 9:28 ` Chaitanya Kulkarni
2022-06-10 9:35 ` Chaitanya Kulkarni
2022-06-10 11:29 ` Hannes Reinecke
2022-06-13 22:29 ` Chaitanya Kulkarni
2022-06-10 9:44 ` 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=7b9bdd9a-1411-ca0d-9f87-71e2c25dffbb@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.