test_ulimit_stack_small in ubuntu_qrt_kernel_security failed on PPC64

Bug #1816467 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned
Nominated for Cosmic by Po-Hsu Lin
Nominated for Disco by Po-Hsu Lin
Nominated for Trusty by Po-Hsu Lin
Nominated for Xenial by Po-Hsu Lin

Bug Description

This test is expecting to throw a return code 137 or 139, but it got 0 instead

ulimit -s 1 && /bin/true
echo $?

After that, if you try to run top command, it will failed with segfault.

FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest)
Ensure small stack limits are enforced
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2855, in test_ulimit_stack_small
self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"]))
File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn
self.assertIn(rc, expected, msg + result + report)
AssertionError: Got exit code 0, expected one of 139, 137
Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true'
Output:

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1816467

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.