On Jun 13, 2024 / 01:20, Christoph Hellwig wrote: > Hi all, > > every since the test was added dm/002 fails for me as shown below. > Does it it need fixes not in mainline yet? The test case always passes for me and I did not expect this failure. I'm not aware of any changes waiting for mainline, both kernel side and blktests side. I would like to take a closer look in the failure, but I can not recreate it on my test systems. I wonder what is the difference between your test system and mine. I guess kernel config difference could be the difference. Could you share your kernel config? > > dm/002 => vdb (dm-dust general functionality test) > [failed]tors > runtime 0.044s ... 0.049son dev dm-0, logical block 8, async page read > --- tests/dm/002.out 2024-06-02 08:38:27.252957357 +0000 > +++ /root/blktests/results/vdb/dm/002.out.bad 2024-06-13 08:19:31.526336224 +0000 > @@ -6,5 +6,3 @@ > dust_clear_badblocks: badblocks cleared > countbadblocks: 0 badblock(s) found > countbadblocks: 3 badblock(s) found > -countbadblocks: 0 badblock(s) found > -Test complete > modprobe: FATAL: Module dm_dust is in use.
