[PATCHv14 00/11] nvme: In-band authentication support

Chaitanya Kulkarni chaitanyak at nvidia.com
Fri Jun 10 02:35:43 PDT 2022 

On 6/10/22 02:28, Chaitanya Kulkarni wrote:
> On 6/10/22 02:12, Hannes Reinecke wrote:
>> On 6/10/22 10:55, Chaitanya Kulkarni wrote:
>>>
>>>>>
>>>>> 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...
>>>
>> Hmm. No, that version looks okay.
>>
>> What's the kernel message log? Does it say something about 
>> 'dev_loss_tmo' ?
>>
>> If so, can you try with 'export nvme_trtype=tcp' and then running the 
>> tests? Previous versions of nvme-cli had issues with nvme-loop, and 
>> were trying to set the 'dev_loss_tmo' parameter, which isn't valid for 
>> loop.
>>
>> Cheers,
> 

Please ignore my earlier log and consider this :-

blktests (master) # nvme_trtype=tcp ./check nvme/039
nvme/039 (Create authenticated connections)                  [failed]
     runtime  1.397s  ...  1.416s
     --- tests/nvme/039.out	2022-06-08 18:09:06.239931529 -0700
     +++ /mnt/data/blktests/results/nodev/nvme/039.out.bad	2022-06-10 
02:34:02.813590992 -0700
     @@ -1,7 +1,9 @@
      Running nvme/039
      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
      NQN:blktests-subsystem-1 disconnected 1 controller(s)
     ...
     (Run 'diff -u tests/nvme/039.out 
/mnt/data/blktests/results/nodev/nvme/039.out.bad' to see the entire diff)
blktests (master) # dmesg  -c
[ 2629.493178] run blktests nvme/039 at 2022-06-10 02:34:01
[ 2629.526813] loop0: detected capacity change from 0 to 1048576
[ 2629.540273] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
[ 2629.540512] nvmet: nvmet_ns_enable_store 535
[ 2629.540516] nvmet: nvmet_ns_enable 555
[ 2629.540518] nvmet: nvmet_ns_enable 559
[ 2629.540519] nvmet: nvmet_ns_enable 565
[ 2629.540520] nvmet: nvmet_ns_enable 573
[ 2629.550996] nvmet: nvmet_ns_enable 580
[ 2629.551005] nvmet: nvmet_ns_enable 596
[ 2629.551007] nvmet: nvmet_ns_enable 601
[ 2629.551008] nvmet: nvmet_ns_enable 605
[ 2629.551009] nvmet: nvmet_ns_enable 607
[ 2629.551010] nvmet: nvmet_ns_enable 610
[ 2629.552027] nvmet_tcp: enabling port 0 (127.0.0.1:4420)
[ 2629.560307] nvmet: creating nvm controller 1 for subsystem 
blktests-subsystem-1 for NQN 
nqn.2014-08.org.nvmexpress:uuid:dfcc37bd-2779-4b29-9f36-7c0386851263 
with DH-HMAC-CHAP.
[ 2629.560343] nvme nvme1: qid 0: no key
[ 2629.560347] nvme nvme1: qid 0: authentication setup failed
[ 2629.560365] nvme nvme1: failed to connect queue: 0 ret=401
[ 2629.577013] nvmet: creating nvm controller 2 for subsystem 
blktests-subsystem-1 for NQN 
nqn.2014-08.org.nvmexpress:uuid:dfcc37bd-2779-4b29-9f36-7c0386851263 
with DH-HMAC-CHAP.
[ 2629.577063] __nvme_auth_work 701
[ 2629.582375] nvme nvme1: qid 0: authenticated with hash hmac(sha256) 
dhgroup null
[ 2629.582395] nvme nvme1: qid 0: authenticated
[ 2629.582863] nvme nvme1: creating 48 I/O queues.
[ 2629.585466] nvme nvme1: mapped 48/0/0 default/read/poll queues.
[ 2629.586634] __nvme_auth_work 701
[ 2629.592092] __nvme_auth_work 701
[ 2629.597131] __nvme_auth_work 701
[ 2629.602217] __nvme_auth_work 701
[ 2629.607362] __nvme_auth_work 701
[ 2629.612357] __nvme_auth_work 701
[ 2629.617396] __nvme_auth_work 701
[ 2629.622605] __nvme_auth_work 701
[ 2629.627642] __nvme_auth_work 701
[ 2629.632645] __nvme_auth_work 701
[ 2629.637676] __nvme_auth_work 701
[ 2629.642738] __nvme_auth_work 701
[ 2629.647647] __nvme_auth_work 701
[ 2629.652817] __nvme_auth_work 701
[ 2629.657795] __nvme_auth_work 701
[ 2629.662618] __nvme_auth_work 701
[ 2629.667358] __nvme_auth_work 701
[ 2629.672319] __nvme_auth_work 701
[ 2629.677234] __nvme_auth_work 701
[ 2629.682177] __nvme_auth_work 701
[ 2629.687177] __nvme_auth_work 701
[ 2629.692211] __nvme_auth_work 701
[ 2629.697234] __nvme_auth_work 701
[ 2629.702091] __nvme_auth_work 701
[ 2629.707177] __nvme_auth_work 701
[ 2629.712087] __nvme_auth_work 701
[ 2629.717093] __nvme_auth_work 701
[ 2629.721979] __nvme_auth_work 701
[ 2629.726928] __nvme_auth_work 701
[ 2629.731843] __nvme_auth_work 701
[ 2629.736852] __nvme_auth_work 701
[ 2629.741845] __nvme_auth_work 701
[ 2629.746871] __nvme_auth_work 701
[ 2629.752102] __nvme_auth_work 701
[ 2629.757202] __nvme_auth_work 701
[ 2629.762209] __nvme_auth_work 701
[ 2629.767301] __nvme_auth_work 701
[ 2629.772238] __nvme_auth_work 701
[ 2629.777158] __nvme_auth_work 701
[ 2629.782157] __nvme_auth_work 701
[ 2629.787153] __nvme_auth_work 701
[ 2629.792119] __nvme_auth_work 701
[ 2629.797402] __nvme_auth_work 701
[ 2629.802400] __nvme_auth_work 701
[ 2629.807405] __nvme_auth_work 701
[ 2629.812316] __nvme_auth_work 701
[ 2629.817405] __nvme_auth_work 701
[ 2629.822526] __nvme_auth_work 701
[ 2629.827648] nvme nvme1: new ctrl: NQN "blktests-subsystem-1", addr 
127.0.0.1:4420
[ 2630.848759] nvme nvme1: Removing ctrl: NQN "blktests-subsystem-1"
[ 2630.881149] nvmet: nvmet_ns_enable_store 535


Let me know if you need any more information, I'll also try and debug
the problem tomorrow.

-ck

More information about the Linux-nvme mailing list