dm-writeboost/2.2.16-0.1ubuntu2 ADT test failure with linux/6.8.0-38.38

[Stefan Bader]

This is a scripted bug report about ADT failures while running dm-writeboost tests for linux/6.8.0-38.38 on noble. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined.

Testing failed on:
    amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/d/dm-writeboost/20240610_173605_e57b9@/log.gz
    arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/d/dm-writeboost/20240610_175139_f777a@/log.gz
    armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/armhf/d/dm-writeboost/20240627_145725_12539@/log.gz
    ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/ppc64el/d/dm-writeboost/20240610_174218_17ff6@/log.gz
    s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/d/dm-writeboost/20240610_184740_ce176@/log.gz

Noble update: v6.8.2 upstream stable release picked up an upstream stable change which added another argument to dm_io().

commit 1fd084870a101c966b50357362ace5b9eba55df3
Author: Hongyu Jin <email address hidden>
Date: Wed Jan 24 13:35:53 2024 +0800

    dm io: Support IO priority

    BugLink: https://bugs.launchpad.net/bugs/2060097

    [ Upstream commit 6e5f0f6383b4896c7e9b943d84b136149d0f45e9 ]

    Some IO will dispatch from kworker with different io_context settings
    than the submitting task, we may need to specify a priority to avoid
    losing priority.

    Add IO priority parameter to dm_io() and update all callers.

[Stefan Bader (smb)]

The kernel follows upstream stable, external DKMS package needs compat update.