Re: SHA1-MB algorithm broken on latest kernel

2016-05-16 Thread Megha Dey
On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote: > On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote: > > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote: > > > * Herbert Xu wrote: > > > > > > > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey

Re: SHA1-MB algorithm broken on latest kernel

2016-05-16 Thread Megha Dey
On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote: > On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote: > > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote: > > > * Herbert Xu wrote: > > > > > > > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > > > > > Hi, > > > >

Re: SHA1-MB algorithm broken on latest kernel

2016-05-16 Thread Josh Poimboeuf
On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote: > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote: > > * Herbert Xu wrote: > > > > > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > > > > Hi, > > > > > > > > When booting latest kernel

Re: SHA1-MB algorithm broken on latest kernel

2016-05-16 Thread Josh Poimboeuf
On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote: > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote: > > * Herbert Xu wrote: > > > > > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > > > > Hi, > > > > > > > > When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB

Re: SHA1-MB algorithm broken on latest kernel

2016-05-13 Thread Megha Dey
On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote: > * Herbert Xu wrote: > > > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > > > Hi, > > > > > > When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I > > > observe a panic. > > > >

Re: SHA1-MB algorithm broken on latest kernel

2016-05-13 Thread Megha Dey
On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote: > * Herbert Xu wrote: > > > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > > > Hi, > > > > > > When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I > > > observe a panic. > > > > > > After having a quick

Re: SHA1-MB algorithm broken on latest kernel

2016-05-12 Thread Ingo Molnar
* Herbert Xu wrote: > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > > Hi, > > > > When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I > > observe a panic. > > > > After having a quick look, on reverting the following patches, I am

Re: SHA1-MB algorithm broken on latest kernel

2016-05-12 Thread Ingo Molnar
* Herbert Xu wrote: > On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > > Hi, > > > > When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I > > observe a panic. > > > > After having a quick look, on reverting the following patches, I am able > > to complete the

Re: SHA1-MB algorithm broken on latest kernel

2016-05-12 Thread Herbert Xu
On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > Hi, > > When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I > observe a panic. > > After having a quick look, on reverting the following patches, I am able > to complete the booting process. >

Re: SHA1-MB algorithm broken on latest kernel

2016-05-12 Thread Herbert Xu
On Thu, May 12, 2016 at 04:31:06PM -0700, Megha Dey wrote: > Hi, > > When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I > observe a panic. > > After having a quick look, on reverting the following patches, I am able > to complete the booting process. >

SHA1-MB algorithm broken on latest kernel

2016-05-12 Thread Megha Dey
Hi, When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I observe a panic. After having a quick look, on reverting the following patches, I am able to complete the booting process. aec4d0e301f17bb143341c82cc44685b8af0b945 8691ccd764f9ecc69a6812dfe76214c86ac9ba06

SHA1-MB algorithm broken on latest kernel

2016-05-12 Thread Megha Dey
Hi, When booting latest kernel with the CONFIG_CRYPTO_SHA1_MB enabled, I observe a panic. After having a quick look, on reverting the following patches, I am able to complete the booting process. aec4d0e301f17bb143341c82cc44685b8af0b945 8691ccd764f9ecc69a6812dfe76214c86ac9ba06