linux: apparmor ADT test failures in changeprofile test

[Andy Whitcroft]

We are seeing ADT test failures in the apparmor kernel regression test suite. We are reporting ENOENT rather than EACCESS:

  running changeprofile
  Error: changeprofile failed. Test 'CHANGEPROFILE (no target, /tmp/sdtest.10794-16623-rfX1oc/file)' was expected to 'fail'. Reason for failure expect errno 13 != 2
  Error: changeprofile failed. Test 'CHANGEPROFILE (no target, /tmp/sdtest.10794-16623-rfX1oc/file2)' was expected to 'fail'. Reason for failure expect errno 13 != 2

This is occuring on amd64, i386 and ppc64el, armhf and s390x are both reporting good:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20160320_121949@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20160320_120702@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20160320_115958@/log.gz

[Andy Whitcroft (apw)]

Confirmed this test failure is only present with 4.4.0-15.31 and downgrading just the kernel makes it go away.

[Steve Beattie (sbeattie)]

Unfortunately, the AppArmor kernel patches that were included in the 4.4.0-15.31 made a slight behavioral change that affects the failing testcases, returning a different error value. As part of landing the user space patches upstream, these have been adjusted in the upstream tests in http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3401 and are expected to land in xenial in the next few days.

The kernel does not need to block on these two failures.

Thanks!

[Andy Whitcroft (apw)]

Thanks will hint those good.

[Steve Beattie (sbeattie)]

AppArmor 2.10.95 landed in xenial, which fixes these failing test cases. Closing bug.