blktests failures with v6.15 kernel

[Daniel Wagner]

Hi,

On Thu, May 29, 2025 at 08:46:35AM +0000, Shinichiro Kawasaki wrote:
> #1: nvme/023
> 
>     When libnvme has version 1.13 or later and built with liburing, nvme-cli
>     command "nvme smart-log" command fails for namespace block devices. This
>     makes the test case nvme/032 fail [2]. Fix in libnvme is expected.
> 
>     [2]
>     https://lore.kernel.org/linux-nvme/32c3e9ef-ab3c-40b5-989a-7aa323f5d611@flourine.local/T/#m6519ce3e641e7011231d955d9002d1078510e3ee

Should be fixed now. If you want, I can do another release soon, so the
fix get packaged up by the distros.

> #2: nvme/041 (fc transport)
> 
>     The test case nvme/041 fails for fc transport. Refer to the report for v6.12
>     kernel [3].
> 
>     [3]
>     https://lore.kernel.org/linux-nvme/6crydkodszx5vq4ieox3jjpwkxtu7mhbohypy24awlo5w7f4k6@to3dcng24rd4/

Is still on my TODO list. Sorry.

> #4: nvme/061 failure (fc transport)
> 
>     The test case nvme/061 sometimes fails due to a WARN [5]. Just before the
>     WARN, The kernel reported "refcount_t: underflow; use-after-free." This
>     failure can be recreated in stable manner by repeating the test case 10
>     times or so.
> 
>     I tried v6.15-rcX kernels. When I ran v6.15-rc1 kernel, the test case always
>     failed with different symptom. With v6.15-rc2 kernel, the test case passed
>     in most runs, but sometimes it failed with the same symptom as v6.15. I
>     guess the nvme-fc changes in v6.15-rc2 fixed most of the refcounting issue,
>     but still rare refcounting failure scenario is left.

The nvmet-fcloop changes for 6.16 should address this (fingers crossed).

Thanks,
Daniel