Re: [LSF/MM/BPF ATTEND][LSF/MM/BPF TOPIC] : blktests: status, expansion plan for the storage stack test framework

[Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>]

On Feb 13, 2026 / 11:23, Shinichiro Kawasaki wrote:
[...]
> Here I share the list of improvement
> opportunities from my view point (I already mentioned the first three items).
> 
>  1. We can have more CI infra to make the most of blktests
>  2. We can add config examples to help new users
>  3. We can measure code coverage to identify missing test areas
>  4. Long standing failures make test result reports dirty
>     - I feel lockdep WARNs are tend to be left unfixed rather long period.
>       How can we gather effort to fix them?
>  5. We can refactor and clean up blktests framework for ease of maintainance
>       (e.g. trap handling)
>  6. Some users run blktests with built-in kernel modules, which makes a number
>     of test cases skipped. We can add more built-in kernel modules support to
>     expand test coverage for such use case.

I read through this e-mail thread again, and revised the list of improvement
opportunities. Hope this list helps the discussion at the session.

 1. configuration example, documentation, or tool for ease of new users
 2. blktests framework capabilitly
   - more bug detection capability (such as kmemleak)
     - code coverage measurement per test case
   - VM integration (virtme-ng? valid use case?)
   - parallel execution for shorter run
   - built-in module testing
   - multi device testing
 3. blktests CI
 4. longstanding failures
   - nvme/005 tcp transport, nbd/002
 5. test area coverage expansion (which area do we lack tests?)
   - code coverage information as the guide
   - new category candidates (rnbd?)
 6. blktests framework refactoring
   - trap handling


One thing I added was "multi device testing". Most of the test cases use
single test device for single test run, while md/003 and bcache/001 require
multiple devices for single test run. There was a discussion how to specify
multiple devices in the config file [*].

[*] https://lore.kernel.org/linux-block/aXHbPWCf5SfycpBX@shinmob/