kernel-packages team mailing list archive

Thread
Date

[Bug 1531327] Re: Various failures of kernel_security suite on Xenial kernel on s390x arch

To: kernel-packages@xxxxxxxxxxxxxxxxxxx
From: Steve Beattie <sbeattie@xxxxxxxxxx>
Date: Tue, 09 Feb 2016 22:58:46 -0000
Reply-to: Bug 1531327 <1531327@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Hi Brad,

I've addressed most of the issues with commit 2464 to the qa-regression-
testing tree. However, there are a few remaining failures that are legit
issues with the kernel on 390x. They are:

FAIL: test_074_config_security_default_mmap_min_addr (__main__.KernelSecurityTest)
CONFIG_DEFAULT_MMAP_MIN_ADDR

CONFIG_DEFAULT_MMAP_MIN_ADDR is set to 4096 on s390x, not 65536 like on
other arches.

FAIL: test_075_config_stack_protector (__main__.KernelSecurityTest)
CONFIG_CC_STACKPROTECTOR set
FAIL: test_082_stack_guard_kernel (__main__.KernelSecurityTest)
Kernel stack guard

CONFIG_CC_STACKPROTECTOR is not set for s390x, unlike for our other
arches. As far as I can tell, gcc and the kernel support the option on
s390x (but if not, then I'll adjust our tests).

I'm also seeing the module tainting test
test_140_kernel_modules_not_tainted failing on s390x. Checking the
contents of /proc/modules, it looks like all the modules on the s390x
kernel (4.4.0-2.16-generic) aren't being signed (i.e. have an (E) listed
for them). I'm not sure why this is, if it indicates an issue with the
kernel build process on s390x.

Thanks.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: qa-regression-testing
       Status: New => Fix Released

-- 
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/1531327

Title:
  Various failures of kernel_security suite on Xenial kernel on s390x
  arch

Status in QA Regression Testing:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Partial log:

  01/05 13:07:05 ERROR|     utils:0153| [stderr] ASLR enabled ... ok
  01/05 13:07:05 ERROR|     utils:0153| [stderr] test_020_aslr_dapper_stack (__main__.KernelSecurityTest)
  01/05 13:07:05 ERROR|     utils:0153| [stderr] ASLR of stack ... ok
  01/05 13:07:05 ERROR|     utils:0153| [stderr] test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
  01/05 13:07:05 ERROR|     utils:0153| [stderr] ASLR of libs ... FAIL
  01/05 13:07:05 ERROR|     utils:0153| [stderr] test_021_aslr_dapper_mmap (__main__.KernelSecurityTest)
  01/05 13:07:05 ERROR|     utils:0153| [stderr] ASLR of mmap ... FAIL
  01/05 13:07:05 ERROR|     utils:0153| [stderr] test_022_aslr_hardy_text (__main__.KernelSecurityTest)
  01/05 13:07:05 ERROR|     utils:0153| [stderr] ASLR of text ... FAIL
  01/05 13:07:05 ERROR|     utils:0153| [stderr] test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
  01/05 13:07:05 ERROR|     utils:0153| [stderr] ASLR of vdso ... FAIL
  01/05 13:07:05 ERROR|     utils:0153| [stderr] test_022_aslr_intrepid_brk (__main__.KernelSecurityTest)
  01/05 13:07:05 ERROR|     utils:0153| [stderr] ASLR of brk ... FAIL

  
  Full log is attached (client.DEBUG.txt).

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1531327/+subscriptions