Message-ID: <55CA4B1F.7030508@cumulusnetworks.com>
Date: Tue, 11 Aug 2015 15:21:03 -0400
From: Jonathan Toppins <jtoppins@cumulusnetworks.com>
Organization: Cumulus Networks
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0
MIME-Version: 1.0
To: Ben Hutchings <ben@decadent.org.uk>, linux-kernel@vger.kernel.org,
        stable@vger.kernel.org
CC: torvalds@linux-foundation.org, Guenter Roeck <linux@roeck-us.net>,
        Phil Jensen <pjensen@evernote.com>, akpm@linux-foundation.org
Subject: Re: [PATCH 3.2 000/110] 3.2.71-rc1 review
References: <lsq.1439201550.905387334@decadent.org.uk>
In-Reply-To: <lsq.1439201550.905387334@decadent.org.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1095
Lines: 30

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.

Maybe this upstream commit is too new and so it will show up in a later 
3.2 stable version?

Thanks,
-Jon

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/