** 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 <torva...@linux-foundation.org> - Date: Mon Aug 22 16:41:46 2016 -0700 + 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 + 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 <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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
