Ubuntu
linux package

ADT security test on linux fails because /proc/self/stack shows 0

Bug #1762500 reported by Thadeu Lima de Souza Cascardo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
Bionic
Incomplete
Undecided
Unassigned

Bug Description

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20180409_125745_f671c@/log.gz

======================================================================
FAIL: test_095_kernel_symbols_missing (__main__.KernelSecurityTest)
kernel addresses in kallsyms and modules are zeroed out
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1521, in test_095_kernel_symbols_missing
    self._check_pK_files(expected)
  File "./test-kernel-security.py", line 1496, in _check_pK_files
    expected, retry=True)
  File "./test-kernel-security.py", line 1378, in _read_twice
    self.assertFalse(0 == int(address, 16), "%s: root saw %s" % (filename, address))
AssertionError: /proc/self/stack: root saw 0

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8f5abe842e84ba9e72485ddd9dc02a3562b54e2a

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 1762500

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
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

The error message has been addressed in bug 1758242, which is also a dup of bug 1751202

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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