Kernel security test test_021_aslr_dapper_libs failed on 3.2 Precise i386

Bug #1717856 reported by Po-Hsu Lin on 2017-09-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QA Regression Testing
Undecided
Unassigned
ubuntu-kernel-tests
Undecided
Unassigned
linux (Ubuntu)
Medium
Unassigned
Precise
Medium
Unassigned

Bug Description

Kernel: 3.2.0-131 Precise (i386)

This is not a regression, as this issue can be reproduced on older kernel.
AMD64 system does not have this issue.

FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 1827, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1790, in _test_aslr
self._test_aslr_all(area, expected, "unlimited stack %s" % area)
File "./test-kernel-security.py", line 1767, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1760, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name)
File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1134, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: unlimited stack libs native:
Got exit code 1, expected 0
Command: './aslr', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0x4002bd80
0x4002bd80
0x4002bd80
FAIL: ASLR not functional (libs always at 0x4002bd80)

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 1717856

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
tags: added: precise
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
status: New → Triaged
Po-Hsu Lin (cypressyew) wrote :

Tested with one of the laptop in the cert lab. (201307-13930)
This issue can be reproduced with 3.2.0-131 but not with 3.2.0-133 in the proposed pocket.

I will leave the bug status as-is, since this is a different node from our normal test pool for regression-testing.

Sean Feole (sfeole) wrote :

Hi Sam, still an issue?

 very old bug, with no action on it, marking bug as incomplete and will close in 5 days if no update.

Changed in ubuntu-kernel-tests:
status: New → Incomplete
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Changed in linux (Ubuntu Precise):
status: Triaged → Incomplete
Po-Hsu Lin (cypressyew) wrote :

This issue can be reproduced on that specific system here.

3.2.0-135 on Precise.

But this test is a little bit flaky, the fail rate for this is about 50%
Just like bug 1747630, sometimes they will appear one-by-one, or even failed together, sometimes they will both pass.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in ubuntu-kernel-tests:
status: Incomplete → Confirmed
Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers