Re:

[Nilay Shroff]

On 8/11/26 2:06 PM, kernel test robot wrote:
> Hello,
>
> kernel test robot noticed "blktests.nvme/048.fail" on:
>
> commit: 657b4cd151e042afc228615869b2a6876b91b8fc ("[PATCH v2 2/4] nvme-tcp: limit I/O queue count based on NIC queue count")
> url: https://github.com/intel-lab-lkp/linux/commits/Nilay-Shroff/net-add-helper-for-device-lookup-by-destination-address/20260731-154725
> patch link: https://lore.kernel.org/all/20260727151652.3660476-3-nilay@xxxxxxxxxxxxx/
> patch subject: [PATCH v2 2/4] nvme-tcp: limit I/O queue count based on NIC queue count
>
> in testcase: blktests
> version: blktests-x86_64-72a6349-1_20260804
> with following parameters:
>
> 	disk: 1SSD
> 	test: nvme-group-02
> 	nvme_trtype: tcp
>
>
>
> config: x86_64-rhel-9.4-func
> compiler: gcc-14
> test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with 32G memory
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
>
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <yi1.lai@xxxxxxxxx>
> | Closes:
> | https://lore.kernel.org/oe-lkp/202608111002.8c383e35-lkp@xxxxxxxxx
>
>
> nvme/048 (tr=tcp) (Test queue count changes on reconnect)
>      runtime  4.358s  ...
> nvme/048 (tr=tcp) (Test queue count changes on reconnect)    [failed]
>      runtime  4.358s  ...  7.340s
>      --- tests/nvme/048.out	2026-08-04 23:49:51.000000000 +0000
>      +++ /mnt/nvme-group-02/nodev_tr_tcp/nvme/048.out.bad	2026-08-06 06:04:55.281322408 +0000
>      @@ -1,2 +1,4 @@
>       Running nvme/048
>      +expected queue count 3 not set
>      +FAIL
>       Test complete
Thanks for the report!

This requires changes in blktests nvme/048. So once this change/commit
is merged upstream, I'd send another patch to update the test.

On another note, you may want to check your automation script which sends
auto-email. I see the email subject line is empty.

Thanks,
--Nilay