I can confirm that openafs-modules-dkms/1.6.15-1ubuntu1.1 can be built and installed on both older and newer xenial/linux kernels:
$ dkms status openafs, 1.6.15, 4.4.0-206-generic, x86_64: installed openafs, 1.6.15, 4.4.0-208-generic, x86_64: installed autopkgtests were also successful: * xenial/linux 4.4.0-208.240 - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210407_161651_8b22b@/log.gz - armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210407_163444_963c5@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/o/openafs/20210407_161429_59fe1@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210407_161222_963c5@/log.gz * xenial/linux 4.4.0-206.238: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210407_142619_8fbc1@/log.gz - armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210407_142941_8fbc1@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/o/openafs/20210407_142002_8fbc1@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210407_142101_8fbc1@/log.gz Note: arm64 and ppc64el has never passed. Thanks, Kleber ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922242 Title: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in openafs package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in openafs source package in Xenial: Fix Committed Bug description: [Impact] autopkgtest caught a build failure with openafs-modules-dkms with the xenial/linux kernel currently in -proposed (4.4.0-207.239). Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz Build error: CC [M] /var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o /var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c: In function ‘osi_UFSTruncate’: /var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12: error: implicit declaration of function ‘inode_change_ok’ [-Werror=implicit-function-declaration] code = inode_change_ok(inode, &newattrs); ^ cc1: some warnings being treated as errors This was caused by commit "fs: Give dentry to inode_change_ok() instead of inode" applied to xenial/linux as part of the fixes for CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare(). [Fix] The proposed fix is to cherry-pick commit 8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git). [Test] Install openafs-modules-dkms on a xenial system running an older kernel without the interface change (<4.4.0-207) and with a newer kernel with the interface change (>=4.4.0-207). The openafs module should be built and loaded with all kernels. [Where problems could occur] The fix is based on the detection made during build time of the function available on the kernel headers. If the detection doesn't work correctly the build would fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
