Date: Thu, 21 Apr 2016 14:50:38 +0200
From: Willy Tarreau <w@1wt.eu>
To: Greg KH <greg@kroah.com>
Cc: Jiri Slaby <jslaby@suse.cz>, Sasha Levin <sasha.levin@oracle.com>,
        LKML <linux-kernel@vger.kernel.org>, stable <stable@vger.kernel.org>,
        lwn@lwn.net
Subject: Re: stable-security kernel updates
Message-ID: <20160421125038.GA9918@1wt.eu>
References: <5717DD8A.4000707@oracle.com>
 <571876AB.2060106@suse.cz>
 <5718B57D.4000504@oracle.com>
 <5718C0B8.8010609@suse.cz>
 <5718C215.7060703@suse.cz>
 <20160421123918.GA2294@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160421123918.GA2294@kroah.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1210
Lines: 26

On Thu, Apr 21, 2016 at 09:39:18PM +0900, Greg KH wrote:
> On Thu, Apr 21, 2016 at 02:05:41PM +0200, Jiri Slaby wrote:
> > On 04/21/2016, 01:59 PM, Jiri Slaby wrote:
> > >> (CVE-2016-2085) 613317b EVM: Use crypto_memneq() for digest comparisons
> > > 
> > > Does not exist in the CVE database/is not confirmed yet AFAICS.
> > 
> > And now I am looking at the patch and I remember why I threw it away.
> > crypto_memneq is not in 3.12 yet and I was not keen enough to backport  it.
> 
> Which brings up the question, Sasha, why did you think these CVEs were
> relevant for 3.12?  What were you basing that list on?

Yep same question here because in fact checking what is *missing* is
harder than checking what should not have been there. I'm pretty sure
I missed a lot of things in 2.6.32 (though Ben and Moritz helped a lot)
but precisely the fact that they provided me fixes I wasn't aware of is
a sign that I can miss things.
 
Any reliable process to check for missing fixes is welcome of course. For
now the best way I found is to pick from more recent stable versions, which
also ensures people upgrading from and older branch to a newer branch will
not find a bug they used to see fixed.

Cheers,
Willy