Qa-testing failures for 2.6.35-903.27

======================================================================
FAIL: Make sure the stack guard page does not split the stack on mlock
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test-kernel.py", line 103, in test_guard_page_split
    self.assertShellExitEquals(expected, ["./split-stack"])
  File "/home/ubuntu/qrt/qrt-test-kernel/testlib.py", line 923, in assertShellExitEquals
    self.assertEquals(expected, rc, msg + result + report)
AssertionError: Got exit code 1, expected 0
Command: './split-stack'
Output:
gap exists in stack VMAs (0x7ea5c000 != 0x7ea5d000)!

for this one, the LP bug is 646114 and it requires 4 patches:

maverick/master
28d2e37 mm: Move vma_stack_continue into mm.h
6bed999 mm: make stack guard page logic use vm_prev pointer
e89cfc4 mm: make the mlock() stack guard page checks stricter
f598143 mm: make the vma list be doubly linked

about SECCOMP:

CONFIG_SECCOMP enabled ... FAIL
...
CONFIG_SECCOMP enabled ... (skipped: not available on ARM) ok

it was not available back then on arm, it entered Linux 2.6.36-rc7 as "70c70d9 ARM: SECCOMP support"

CONFIG_STRICT_DEVMEM enabled ... FAIL
/dev/mem unreadable for kernel memory ... (exit code 5) FAIL

same as SECCOMP, entered Linux 2.6.36-rc7 as "087aaff ARM: implement CONFIG_STRICT_DEVMEM by disabling access to RAM via /dev/mem"

while for Yama we need:

maverick/master
2d8035 Yama: fix default relationship to check thread group
4af9ec Yama: use thread group leader when creating match

respectively LP737676 and LP729839

This bug is awaiting verification that the kernel in -proposed solves the problem (linux-ti-omap4 2.6.35-903.28). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-maverick' to 'verification-done-maverick'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Since this is related to QA tests, real verification will be done in QA (regression-testing) after verification, and will fail if it's not solved on QA, thus marking as verification-done.

This bug was fixed in the package linux-ti-omap4 - 2.6.35-903.28

---------------
linux-ti-omap4 (2.6.35-903.28) maverick-proposed; urgency=low

  * Release Tracking Bug
    - LP: #897740

  [ Upstream Kernel Changes ]

  * crypto: ghash - Avoid null pointer dereference if no key is set
    - LP: #887299
    - CVE-2011-4081
  * xfs: Fix possible memory corruption in xfs_readlink, CVE-2011-4077
    - LP: #887298
    - CVE-2011-4077
  * jbd/jbd2: validate sb->s_first in journal_get_superblock()
    - LP: #893148
    - CVE-2011-4132
  * hfs: add sanity check for file name length, CVE-2011-4330
    - LP: #894374
    - CVE-2011-4330
  * ipv6: udp: fix the wrong headroom check
    - LP: #894373
    - CVE-2011-4326
  * mm: make the vma list be doubly linked
    - LP: #893190
  * mm: make the mlock() stack guard page checks stricter
    - LP: #893190
  * mm: make stack guard page logic use vm_prev pointer
    - LP: #893190
  * mm: Move vma_stack_continue into mm.h
    - LP: #672664, #893190
  * Yama: fix default relationship to check thread group
    - LP: #737676, #893190
  * Yama: use thread group leader when creating match
    - LP: #729839, #893190
 -- Paolo Pisati <email address hidden> Fri, 02 Dec 2011 13:04:02 +0100