dm-writeboost 2.1.1-1 ADT test failure with linux-hwe 4.8.0-37.39~16.04.2

[Andy Whitcroft]

SRU Justification:

Impact: When we add the Yakkety/4.8 kernel as HWE option for Xenial this would break DKMS build of dm-writeboost.

Fix: Add compat code to allow compiling with a 4.8 kernel.

Testcase: dkms build for 4.4 and 4.8 kernels in xenial.

---

Testing failed on:
    amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/d/dm-writeboost/20170205_185303_4085d@/log.gz
    armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/armhf/d/dm-writeboost/20170205_185346_4085d@/log.gz
    i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/i386/d/dm-writeboost/20170205_185300_4085d@/log.gz
    ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/ppc64el/d/dm-writeboost/20170205_185438_4085d@/log.gz
    s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-canonical-kernel-team-unstable/xenial/s390x/d/dm-writeboost/20170205_184702_4085d@/log.gz

[Akira Hayakawa (ruby-wktk)]

I am the upstream maintainer of this module.
The compilation problem has been fixed as of version 2.2.6.
https://github.com/akiradeveloper/dm-writeboost/commit/08b96fcad9d223aa80f9ac76ddb677e056066b48
I recommend all users to upgrade to the latest version immediately because some other important fixes are included since 2.1.1.

By the way, I will release 2.2.7 or 2.3.0 soon. Keep watching.

[Andy Whitcroft (apw)]

Hello Andy, or anyone else affected,

Accepted dm-writeboost into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dm-writeboost/2.1.1-1ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Stefan Bader (smb)]

Thanks Akira, we probably should think about a 2.2.6 upgrade then. But usually to backport complete new versions into older releases needs to be argued with the archive admins. At least if the delta is larger. But sounds like worth following up on at latest when we have to go through this again once the next release will be available back in xenial.

[Stefan Bader (smb)]

ii dm-writeboost-dkms 2.1.1-1ubuntu1

#> dkms status
dm-writeboost, 2.1.1, 4.4.0-67-generic, x86_64: installed
dm-writeboost, 2.1.1, 4.8.0-42-generic, x86_64: installed

[Launchpad Janitor (janitor)]

This bug was fixed in the package dm-writeboost - 2.1.1-1ubuntu1

---------------
dm-writeboost (2.1.1-1ubuntu1) xenial; urgency=medium

  * Add kernel 4.6/4.8 compat code (LP: #1662107)

 -- Stefan Bader <email address hidden> Mon, 06 Feb 2017 11:39:32 +0100

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for dm-writeboost has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.