On Tue, 2015-08-11 at 15:21 -0400, Jonathan Toppins wrote:
> On 08/10/2015 06:12 AM, Ben Hutchings wrote:
> > This is the start of the stable review cycle for the 3.2.71 release.
> > There are 110 patches in this series, which will be posted as responses
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed Aug 12 11:00:00 UTC 2015.
> > Anything received after that time might be too late.
> >
> > A combined patch relative to 3.2.70 will be posted as an additional
> > response to this. A shortlog and diffstat can be found below.
> >
>
> Was thinking I would see upstream commit
> b6878d9e03043695dbf3fa1caa6dfc09db225b16, overlooked?
>
> Has been backported by at least Debian in their 3.2 kernel, version
> 3.2.68-1+deb7u3, to fix CVE-2015-5697.
Funnily enough, I am aware of that. :-)
> Maybe this upstream commit is too new and so it will show up in a later
> 3.2 stable version?
Yes, it is too new (only released in 4.2-rc6, and I looked for fixes up
to 4.2-rc5).
Ben.
--
Ben Hutchings
Theory and practice are closer in theory than in practice.
- John Levine, moderator of comp.compilers
Attachment:
signature.asc
Description: This is a digitally signed message part