I noticed that failure too, tested it manually on trusty amd64 with both 64-bit and 32-bit binary, and with 3.2 kernel, and it worked fine. I'll try the whole suite on a precise VM and see if I can reproduce it.
-- 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/1747847 Title: Tests in ubuntu_qrt_kernel_security (021, 022) complains about ASLR not functional on Trusty ARM64 Status in QA Regression Testing: Confirmed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: This was reported in bug 1630000 I think it's better it tear it down into pieces. FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ---------------------------------------------------------------------- Traceback (most recent call last): File "./test-kernel-security.py", line 1832, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1795, in _test_aslr self._test_aslr_all(area, expected, "unlimited stack %s" % area) File "./test-kernel-security.py", line 1772, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1765, 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: 0x0000200002f130 0x0000200002f130 0x0000200002f130 FAIL: ASLR not functional (libs always at 0x0000200002f130) ====================================================================== FAIL: test_021_aslr_dapper_mmap (__main__.KernelSecurityTest) ASLR of mmap ---------------------------------------------------------------------- Traceback (most recent call last): File "./test-kernel-security.py", line 1817, in test_021_aslr_dapper_mmap self._test_aslr('mmap', expected) File "./test-kernel-security.py", line 1795, in _test_aslr self._test_aslr_all(area, expected, "unlimited stack %s" % area) File "./test-kernel-security.py", line 1772, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1765, 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 mmap native: Got exit code 1, expected 0 Command: './aslr', 'mmap', '--verbose' Output: Checking ASLR of mmap: 0x0000200018e010 0x0000200018e010 0x0000200018e010 FAIL: ASLR not functional (mmap always at 0x0000200018e010) ====================================================================== FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest) ASLR of vdso ---------------------------------------------------------------------- Traceback (most recent call last): File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso self._test_aslr('vdso', expected) File "./test-kernel-security.py", line 1795, in _test_aslr self._test_aslr_all(area, expected, "unlimited stack %s" % area) File "./test-kernel-security.py", line 1772, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1765, 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 vdso native: Got exit code 1, expected 0 Command: './aslr', 'vdso', '--verbose' Output: Checking ASLR of vdso: 0x0000200001c000 0x0000200001c000 0x0000200001c000 FAIL: ASLR not functional (vdso always at 0x0000200001c000) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-141-generic 3.13.0-141.190 ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39 Uname: Linux 3.13.0-141-generic aarch64 NonfreeKernelModules: signpost AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.27 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: Date: Wed Feb 7 06:51:21 2018 Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-3.13.0-141-generic N/A linux-backports-modules-3.13.0-141-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1747847/+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