[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
** Changed in: apparmor (Ubuntu) Status: New => Fix Released ** Changed in: apparmor Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid -- 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/1630069 Title: Regression tests can not detect binfmt_elf mmpa semantic change Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in linux source package in Xenial: Invalid 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 TorvaldsDate: 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
This bug was fixed in the package apparmor - 2.10.95-0ubuntu2.5 --- apparmor (2.10.95-0ubuntu2.5) xenial; urgency=medium * debian/lib/apparmor/functions, debian/apparmor.init, debian/apparmor.service, debian/apparmor.upstart, debian/lib/apparmor/profile-load: Adjust the checks that previously kept AppArmor policy from being loaded while booting a container. Now we attempt to load policy if we're in a LXD or LXC managed container that is using profile stacking inside of a policy namespace. (LP: #1628285) * Fix regression tests for stacking so that the kernel SRU process is not interrupted by failing tests whenever the AppArmor stacking features are backported from the 16.10 kernel or when the 16.04 LTS Enablement Stack receives a 4.8 or newer kernel - debian/patches/r3509-tests-fix-exec_stack-errors-1.patch: Fix the exec_stack.sh test when running on 4.8 or newer kernels (LP: #1628745) - debian/patches/r3558-tests-fix-exec_stack-errors-2.patch: Adjust the exec_stack.sh fix mentioned above to more accurately test kernels older than 4.8 (LP: #1630069) - debian/patches/allow-stacking-tests-to-use-system.patch: Apply this patch earlier in the series, as to match when it was committed upstream, so that the above two patches can be cherry-picked from lp:apparmor -- Tyler HicksFri, 07 Oct 2016 05:21:44 + ** Changed in: apparmor (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/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 Released 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 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
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 Kernel Packages, which is subscribed to linux 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 TorvaldsDate: 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
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 Kernel Packages, which is subscribed to linux 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 TorvaldsDate: 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
This bug was fixed in the package linux - 4.8.0-21.23 --- linux (4.8.0-21.23) yakkety; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1630279 * powerpc 4.8.0-17 fails to boot on PowerMac G5 (LP: #1628968) - Revert "Revert "powerpc: Simplify module TOC handling"" * Regression tests can not detect binfmt_elf mmpa semantic change (LP: #1630069) - SAUCE: apparmor: add flag to detect semantic change, to binfmt_elf mmap * Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40 (LP: #1629204) - SAUCE: (namespace) autofs4: Use real_cred for requestor's ids -- Tim GardnerTue, 04 Oct 2016 08:01:21 -0600 ** Changed in: linux (Ubuntu Yakkety) Status: In Progress => Fix Released -- 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/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: In Progress 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 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
** Description changed: == apparmor SRU == [Impact] - * The exec_stack.sh regression test fails due to a behavior change in 4.8 -kernels from this patch: + * The exec_stack.sh regression test fails due to a behavior change in 4.8 + kernels from this patch: -commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 -Author: Linus Torvalds-Date: Mon Aug 22 16:41:46 2016 -0700 + commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 + Author: Linus Torvalds + Date: Mon Aug 22 16:41:46 2016 -0700 -binfmt_elf: switch to new creds when switching to new mm + 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). + * 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 - $ cd tests/regression/apparmor - $ make USE_SYSTEM=1 - $ sudo bash exec_stack.sh + $ 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. + 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. + * 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: + * Fixed in upstream lp:apparmor tree: -https://bazaar.launchpad.net/~apparmor- + 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. -- 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/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: In Progress Status in apparmor source package in Xenial: In Progress 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: In Progress 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 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
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
The Yakkety apparmor package does not need this change since the Yakkety kernel will always have kernel commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46 present. ** Description changed: + == 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+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 + $ 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. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu Yakkety) Status: New => Won't Fix ** Changed in: apparmor (Ubuntu Xenial) Status: New => In Progress ** Changed in: apparmor (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: apparmor (Ubuntu Xenial) Assignee: (unassigned) => Tyler Hicks (tyhicks) -- 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/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: In Progress Status in apparmor source package in Xenial: In Progress 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: In Progress 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 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 $ 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630069] Re: Regression tests can not detect binfmt_elf mmpa semantic change
** Changed in: apparmor Status: New => Fix Committed ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => In Progress -- 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/1630069 Title: Regression tests can not detect binfmt_elf mmpa semantic change Status in AppArmor: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp