Re: [PATCH] crypto: sha256_ssse3 - fix stack corruption with SSSE3 and AVX implementations

2013-05-22 Thread Tim Chen
On Tue, 2013-05-21 at 17:09 +0300, Jussi Kivilinna wrote: > The _XFER stack element size was set too small, 8 bytes, when it needs to be > 16 bytes. As _XFER is the last stack element used by these implementations, > the 16 byte stores with 'movdqa' corrupt the stack where the value of register > %

[PATCH] crypto: ux50: Cocci spatch "resource_size.spatch"

2013-05-22 Thread Thomas Meyer
Signed-off-by: Thomas Meyer --- diff -u -p a/drivers/crypto/ux500/cryp/cryp_core.c b/drivers/crypto/ux500/cryp/cryp_core.c --- a/drivers/crypto/ux500/cryp/cryp_core.c +++ b/drivers/crypto/ux500/cryp/cryp_core.c @@ -1600,7 +1600,7 @@ static int ux500_cryp_remove(struct plat res = platf

Re: [PATCH][RFC] CPU Jitter random number generator (resent)

2013-05-22 Thread Stephan Mueller
On Wed, 22 May 2013 13:40:04 -0400 Sandy Harris wrote: Hi Sandy, > Stephan Mueller wrote: > > > Ted is right that the non-deterministic behavior is caused by the OS > > due to its complexity. ... > > >> > For VM's, it means we should definitely use > >> > paravirtualization to get randomness

Re: [PATCH][RFC] CPU Jitter random number generator (resent)

2013-05-22 Thread Sandy Harris
Stephan Mueller wrote: > Ted is right that the non-deterministic behavior is caused by the OS > due to its complexity. ... >> > For VM's, it means we should definitely use >> > paravirtualization to get randomness from the host OS. >> ... > > That is already in place at least with KVM and Xen a

Re: [PATCH] crypto: sha256_ssse3 - fix stack corruption with SSSE3 and AVX implementations

2013-05-22 Thread Julian Wollrath
Hi, > The _XFER stack element size was set too small, 8 bytes, when it > needs to be 16 bytes. As _XFER is the last stack element used by > these implementations, the 16 byte stores with 'movdqa' corrupt the > stack where the value of register %r12 is temporarily stored. As > these implementations