On Thursday, May 08, 2014 at 03:30:25 PM, Herbert Xu wrote:
> On Wed, Apr 30, 2014 at 03:17:54PM -0400, Milos Vyletel wrote:
> > Coverity detected possible use of uninitialized pointer when printing
> > info message during module load. While this is higly unlikely to cause
> > any troubles simple
On Thursday, May 08, 2014 at 03:30:25 PM, Herbert Xu wrote:
On Wed, Apr 30, 2014 at 03:17:54PM -0400, Milos Vyletel wrote:
Coverity detected possible use of uninitialized pointer when printing
info message during module load. While this is higly unlikely to cause
any troubles simple change
On Wed, Apr 30, 2014 at 03:17:54PM -0400, Milos Vyletel wrote:
> Coverity detected possible use of uninitialized pointer when printing info
> message during module load. While this is higly unlikely to cause any troubles
> simple change in sha1_ssse3_mod_init to make it look like sha256/512 init
>
On Wed, Apr 30, 2014 at 03:17:54PM -0400, Milos Vyletel wrote:
Coverity detected possible use of uninitialized pointer when printing info
message during module load. While this is higly unlikely to cause any troubles
simple change in sha1_ssse3_mod_init to make it look like sha256/512 init
Hi!
> Most likely yes but I wanted to keep sha1_ssse3_mod_init consistent
> with sha256_ssse3_mod_init/sha512_ssse3_mod_init functions.
> > > Reported-by:
> > > Signed-off-by: Milos Vyletel
> > > ---
> > > arch/x86/crypto/sha1_ssse3_glue.c | 22 --
> > > 1 file changed,
And this time in plain text...
Most likely yes but I wanted to keep sha1_ssse3_mod_init consistent
with sha256_ssse3_mod_init/sha512_ssse3_mod_init functions.
Milos
On Tue, May 6, 2014 at 4:28 AM, Pavel Machek wrote:
> On Wed 2014-04-30 15:17:54, Milos Vyletel wrote:
>> Coverity detected
On Wed 2014-04-30 15:17:54, Milos Vyletel wrote:
> Coverity detected possible use of uninitialized pointer when printing info
> message during module load. While this is higly unlikely to cause any troubles
> simple change in sha1_ssse3_mod_init to make it look like sha256/512 init
> function will
On Wed 2014-04-30 15:17:54, Milos Vyletel wrote:
Coverity detected possible use of uninitialized pointer when printing info
message during module load. While this is higly unlikely to cause any troubles
simple change in sha1_ssse3_mod_init to make it look like sha256/512 init
function will fix
And this time in plain text...
Most likely yes but I wanted to keep sha1_ssse3_mod_init consistent
with sha256_ssse3_mod_init/sha512_ssse3_mod_init functions.
Milos
On Tue, May 6, 2014 at 4:28 AM, Pavel Machek pa...@ucw.cz wrote:
On Wed 2014-04-30 15:17:54, Milos Vyletel wrote:
Coverity
Hi!
Most likely yes but I wanted to keep sha1_ssse3_mod_init consistent
with sha256_ssse3_mod_init/sha512_ssse3_mod_init functions.
Reported-by: scan-ad...@coverity.com
Signed-off-by: Milos Vyletel milos.vyle...@gmail.com
---
arch/x86/crypto/sha1_ssse3_glue.c | 22
Coverity detected possible use of uninitialized pointer when printing info
message during module load. While this is higly unlikely to cause any troubles
simple change in sha1_ssse3_mod_init to make it look like sha256/512 init
function will fix this.
260
6. Condition sha1_transform_asm,
Coverity detected possible use of uninitialized pointer when printing info
message during module load. While this is higly unlikely to cause any troubles
simple change in sha1_ssse3_mod_init to make it look like sha256/512 init
function will fix this.
260
6. Condition sha1_transform_asm,
12 matches
Mail list logo
