I've completed the AppArmor test plan: https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
I've also manually verified the AppArmor portion of this SRU with the kernel currently in xenial-updates (4.4.0-45.66) and the kernel in xenial-proposed (4.4.0-46.67), which contains a number of AppArmor changes. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1628295 Title: Change in kernel stacking behavior causes regression tests to fail Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Trusty: New Status in apparmor source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Bug description: [Impact] * Two regression tests fail due to a behavior change in recent Xenial and Yakkety kernels * Adjusting the regression tests appropriately allows the kernel and security teams to use QRT's test-apparmor.py to test kernel and userspace AppArmor changes with confidence [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 stackonexec.sh Error: transition failed. Test 'STACKONEXEC (stacked with unconfined - okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode "enforce" != expected_mode "mixed"' Error: transition passed. Test 'STACKONEXEC (stacked with unconfined - bad mode)' was expected to 'fail' $ sudo bash stackprofile.sh Error: transition failed. Test 'STACKPROFILE (stacked with unconfined - okcon)' was expected to 'pass'. Reason for failure 'FAIL - current mode "enforce" != expected_mode "mixed"' The two previous commands should result in no output and return value of 0 once the regression test is properly updated. [Regression Potential] * This is an extremely low risk change since it only touches regression testing code that is not user-facing. [Other Info] * This bug has already been fixed upstream: https://bazaar.launchpad.net/~apparmor- dev/apparmor/master/revision/3505 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
