[bug report] most of blktests nvme/ failed on the latest linux tree

[Chaitanya Kulkarni]

On 6/27/23 09:33, Yi Zhang wrote:
> Hello
>
> I found this failure on the latest linux tree, and it cannot be
> reproduced on v6.4,
> it should be one regression recently merged to linux tree after v6.4.
> I check the commit recently merged after v6.4, and found below commit
> touched the related code, not sure if it was introduced by this
> commit.
>
> commit 959ffef13bac792e4e2e3321d6e2bd2b00c0f5f9
> Author: Chaitanya Kulkarni <kch at nvidia.com>
> Date:   Thu Jun 1 23:47:42 2023 -0700
>
>      nvme-fabrics: open code __nvmf_host_find()
>
> [  524.706158] run blktests nvme/004 at 2023-06-27 02:00:43
> [  524.779499] loop0: detected capacity change from 0 to 2097152
> [  524.790075] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
> [  524.810743] nvme_fabrics: found same hostid
> 08dfb4e9-d246-4450-afb6-bc6249f9dc96 but different hostnqn
> nqn.2014-08.org.nvmexpress:uuid:4c4c4544-005a-3010-804b-b4c04f4e3232
> [  525.346603] run blktests nvme/006 at 2023-06-27 02:00:44
> [  525.380421] loop0: detected capacity change from 0 to 2097152
> [  525.391846] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
> [  525.901516] run blktests nvme/007 at 2023-06-27 02:00:45
> [  525.934980] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
> [  526.412792] run blktests nvme/008 at 2023-06-27 02:00:45
> [  526.446070] loop0: detected capacity change from 0 to 2097152
> [  526.456790] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
> [  526.471220] nvme_fabrics: found same hostid
> 1cb04df4-a83c-4257-84ad-aa5dab3e961c but different hostnqn
> nqn.2014-08.org.nvmexpress:uuid:4c4c4544-005a-3010-804b-b4c04f4e3232
> [  527.014108] run blktests nvme/009 at 2023-06-27 02:00:46
> [  527.045095] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
> [  527.059680] nvme_fabrics: found same hostid
> 1584c36e-4a26-4408-a7d6-5608c0197141 but different hostnqn
> nqn.2014-08.org.nvmexpress:uuid:4c4c4544-005a-3010-804b-b4c04f4e3232
>
>

Looking into it on nvme tree with latest branch nvme-6.5,
will get back to you soon ...

-ck