blktests failures with v6.1
Christoph Hellwig
hch at infradead.org
Thu Dec 22 23:23:59 PST 2022
On Fri, Dec 23, 2022 at 04:50:42AM +0000, Shinichiro Kawasaki wrote:
> The test case fails with NVME devices due to lockdep WARNING "possible
> circular locking dependency detected". Reported in September [1] and solution
> was discussed. A kernel fix patch was posted [2]. It may not be the best fix.
>
> [1] https://lore.kernel.org/linux-block/20220930001943.zdbvolc3gkekfmcv@shindev/
> [2] https://lore.kernel.org/linux-nvme/20221012080318.705449-1-shinichiro.kawasaki@wdc.com/
>
> This test case shows different failure symptom with HDDs. Need further
> investigation.
Yes. Not a huge fan of the fix, but we need to look into this.
Sorry for delaying this so long, I'll try to look into this.
> #2: block/024
>
> Fails on slow machines. I suspect test case needs improvement.
> Need further investigation.
>
> block/024 (do I/O faster than a jiffy and check iostats times) [failed]
> runtime ... 4.347s
> --- tests/block/024.out 2022-12-06 20:51:41.525066605 +0900
> +++ /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/block/024.out.bad 2022-12-07 12:51:03.610924521 +0900
> @@ -6,5 +6,5 @@
> read 1 s
> write 1 s
> read 2 s
> -write 3 s
> +write 4 s
Yes, I've been seeing this for a while as well.
> #3: nvme/002
> #4: nvme/016
> #5: nvme/017
>
> The test cases fail with similar messages below. Reported in June [3].
> Fixes in the test cases are expected.
I think this is related to the current NQN that Hannes added.
Hannes, can you look into this?
More information about the Linux-nvme
mailing list