Hello John, or anyone else affected, Accepted apparmor into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.5 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! ** Changed in: apparmor (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1630069 Title: Regression tests can not detect binfmt_elf mmpa semantic change Status in AppArmor: Fix Committed Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Committed Status in linux source package in Xenial: New Status in apparmor source package in Yakkety: Won't Fix Status in linux source package in Yakkety: Fix Released Bug description: == apparmor SRU == [Impact] * The exec_stack.sh regression test fails due to a behavior change in 4.8 kernels from this patch: commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 Author: Linus Torvalds <torva...@linux-foundation.org> Date: Mon Aug 22 16:41:46 2016 -0700 binfmt_elf: switch to new creds when switching to new mm * The regression tests were fixed for this kernel change but they were fixed in a way that always assumed that kernel change is present. They should have been adjusted so that they act differently according to whether or not the kernel change is present (it is a change that could end up being backported through the stable trees). [Test Case] $ apt-get source apparmor # make sure this fetches the new apparmor source $ sudo apt-get install libapparmor-dev $ cd tests/regression/apparmor $ make USE_SYSTEM=1 $ sudo bash exec_stack.sh The previous command should result in no output and return value of 0. [Regression Potential] * This is an extremely low risk change since it only touches regression testing code that is not user-facing. [Other] * Fixed in upstream lp:apparmor tree: https://bazaar.launchpad.net/~apparmor- dev/apparmor/master/revision/3558 == Original description == The regression tests are currently hard coded to the semantics of mmap in binfmt_elf With the recent upstream commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 the cred used for the mmap changed resulting in test failures. The tests have been patched for this change but it results in the test breaking for everyone using upstream releases against pre 4.8 kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1630069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : email@example.com Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp