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: #
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.
** Tags removed: verification-needed-maverick
** Tags added: verification-done-maverick
--
You received this
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
** Branch linked: lp:ubuntu/maverick-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893190
Title:
Qa-testing failures for 2.6.35-903.27
To manage notifications about this bug
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Status: New => Fix Committed
** Changed in: linux-ti-omap4 (Ubuntu Maverick)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- During the qa-testing of 2.6.35-903.27 several missing config options
- went uncovered, the complete logs are available here:
+ During the qa-testing of 2.6.35-903.27 several missing patches went
+ uncovered, the complete logs are available here:
https://bugs.launchp
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
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"
--
You received this bug notification because you are a member of
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"
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
==
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_
** Also affects: linux-ti-omap4 (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: linux-ti-omap4 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
11 matches
Mail list logo
