kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #68955
[Bug 1335049] Re: Lucid update to 2.6.32.63 stable release
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from Linus' tree or in a minimally
+ backported form of that patch. The 2.6.32.63 upstream stable
+ patch set is now available. It should be included in the Ubuntu
+ kernel as well.
- Impact:
- The upstream process for stable tree updates is quite similar
- in scope to the Ubuntu SRU process, e.g., each patch has to
- demonstrably fix a bug, and each patch is vetted by upstream
- by originating either directly from Linus' tree or in a minimally
- backported form of that patch. The 2.6.32.63 upstream stable
- patch set is now available. It should be included in the Ubuntu
- kernel as well.
+ git://git.kernel.org/
- git://git.kernel.org/
+ TEST CASE: TBD
- TEST CASE: TBD
+ The following patches are in the 2.6.32.63 stable release:
- The following patches are in the 2.6.32.63 stable release:
+ Linux 2.6.32.63
+ net: fix regression introduced in 2.6.32.62 by sysctl fixes
+ auditsc: audit_krule mask accesses need bounds checking
+ futex: Prevent attaching to kernel threads
+ ethtool: Report link-down while interface is down
+
+ The following patches from 2.6.32.63 were not applied as they were
+ already present in the Lucid kernel:
+
+ futex: Make lookup_pi_state more robust
+ futex: Always cleanup owner tid in unlock_pi
+ futex: Validate atomic acquisition in futex_lock_pi_atomic()
+ futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)
+
+ The following patch from 2.6.32.63 was dropped as one of futex patches
+ in Lucid seem to implement a slightly different security fix that
+ prevents it from being applied:
+
+ futex: Add another early deadlock detection check
--
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/1335049
Title:
Lucid update to 2.6.32.63 stable release
Status in “linux” package in Ubuntu:
New
Status in “linux” source package in Lucid:
New
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from Linus' tree or in a minimally
backported form of that patch. The 2.6.32.63 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches are in the 2.6.32.63 stable release:
Linux 2.6.32.63
net: fix regression introduced in 2.6.32.62 by sysctl fixes
auditsc: audit_krule mask accesses need bounds checking
futex: Prevent attaching to kernel threads
ethtool: Report link-down while interface is down
The following patches from 2.6.32.63 were not applied as they were
already present in the Lucid kernel:
futex: Make lookup_pi_state more robust
futex: Always cleanup owner tid in unlock_pi
futex: Validate atomic acquisition in futex_lock_pi_atomic()
futex-prevent-requeue-pi-on-same-futex.patch futex: Forbid uaddr == uaddr2 in futex_requeue(..., requeue_pi=1)
The following patch from 2.6.32.63 was dropped as one of futex patches
in Lucid seem to implement a slightly different security fix that
prevents it from being applied:
futex: Add another early deadlock detection check
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1335049/+subscriptions
References