I reviewed your list against 3.2.y: On Fri, 2013-03-15 at 09:27 +0100, Jiri Slaby wrote: > Hi, > > we have the following commits from usptream in a SLE11sp2 kernel (3.0) > to fix various CVEs: > Git-commit: 3118a4f652c7b12c752f3222af0447008f9b2368 What's that then? > Git-commit: b0de59b5733d18b0d1974a060860a8b5c1b36a2e The commit message says: Cc: stable <stable@xxxxxxxxxxxxxxx> # after 3.9 is out Should we keep waiting? > Git-commit: b5a1eeef04cc7859f34dec9b72ea1b28e4aba07c > Git-commit: c00b6856fc642b234895cfabd15b289e76726430 > Git-commit: 08dff7b7d629807dbb1f398c68dd9cd58dd657a1 I've queued these up. The last required a trivial adjustment as build_all_zonelists() only takes one parameter. > Git-commit: 8d0c2d10dd72c5292eda7a06231056a4c972e4cc Upstream version applied cleanly and is already in my patch queue. > Git-commit: d780592b99d7d8a5ff905f6bacca519d4a342c76 > Git-commit: 0924ab2cfa98b1ece26c033d696651fd62896c69 > Git-commit: cb101ed2c3c7c0224d16953fe77bfb9d6c2cb9df > Git-commit: c7fd0d48bde943e228e9c28ce971a22d6a1744c4 Already included in 3.2.0. > Git-commit: 3e515705a1f46beb1c942bb8043c16f8ac7b1e9e > Git-commit: 6d1068b3a98519247d8ba4ec85cd40ac136dbdf9 > Git-commit: f2ebd422f71cda9c791f76f85d2ca102ae34a1ed > Git-commit: b92946e2919134ebe2a4083e4302236295ea2a73 > Git-commit: bf118a342f10dafe44b14451a1392c3254629a1f Already backported in 3.2.y. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity.
Attachment:
signature.asc
Description: This is a digitally signed message part