On Sat, 2016-03-19 at 10:23 +0800, Herbert Xu wrote:
> On Fri, Mar 18, 2016 at 10:34:23AM -0700, Greg KH wrote:
> >
> > On Fri, Mar 18, 2016 at 10:42:40PM +0800, Herbert Xu wrote:
> > >
> > > This bug has already bee fixed upstream since 4.2. However, it
> > > was fixed during the AEAD conversion so no fix was backported to
> > > the older kernels.
> > What was the commit id of that fix?
> commit adcbc688fe2f8107b7f564187593293aa9ea3932
> Author: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
> Date: Tue Jun 16 13:54:18 2015 +0800
>
> crypto: gcm - Convert to new AEAD interface
>
> >
> > What stable kernel(s) do you want this in?
> Since the fix was merged in 4.2 this is needed on all kernels
> prior to that, i.e., 4.1 and any prior version.
It looks like the bug was introduced in 3.10 by:
d733ac90f9fe8ac284e523f9920b507555b12f6d
Author: Jussi Kivilinna <jussi.kivilinna@xxxxxx>
Date: Sun Apr 7 16:43:46 2013 +0300
crypto: gcm - fix rfc4543 to handle async crypto correctly
So 3.2.y and 3.4.y don't need this fix - or should they get both fixes?
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
Attachment:
signature.asc
Description: This is a digitally signed message part
