kernel.git/arch/sparc/crypto, branch linux-3.10.y

crypto: sparc - initialize blkcipher.ivsize

2015-10-27T00:44:49Z

commit a66d7f724a96d6fd279bfbd2ee488def6b081bea upstream. Some of the crypto algorithms write to the initialization vector, but no space has been allocated for it. This clobbers adjacent memory. Signed-off-by: Dave Kleikamp Signed-off-by: Herbert Xu Signed-off-by: Greg Kroah-Hartman

crypto: prefix module autoloading with "crypto-"

2015-01-30T01:40:57Z

commit 5d26a105b5a73e5635eae0629b42fa0a90e07b7b upstream. This prefixes all crypto module loading with "crypto-" so we never run the risk of exposing module auto-loading to userspace via a crypto API, as demonstrated by Mathias Krause: https://lkml.org/lkml/2013/3/4/70 Signed-off-by: Kees Cook Signed-off-by: Herbert Xu Signed-off-by: Greg Kroah-Hartman

sparc64: Set CRYPTO_TFM_REQ_MAY_SLEEP consistently in CAMELLIA code.

2012-12-19T23:44:31Z

We use the FPU and therefore cannot sleep during the crypto loops. Signed-off-by: David S. Miller

sparc64: Set CRYPTO_TFM_REQ_MAY_SLEEP consistently in DES code.

2012-12-19T23:43:38Z

We use the FPU and therefore cannot sleep during the crypto loops. Signed-off-by: David S. Miller

sparc64: Fix ECB looping constructs in AES code.

2012-12-19T23:30:07Z

Things works better when you increment the source buffer pointer properly. Signed-off-by: David S. Miller

sparc64: Set CRYPTO_TFM_REQ_MAY_SLEEP consistently in AES code.

2012-12-19T23:22:03Z

We use the FPU and therefore cannot sleep during the crypto loops. Signed-off-by: David S. Miller

sparc64: Fix AES ctr mode block size.

2012-12-19T23:20:23Z

Like the generic versions, we need to support a block size of '1' for CTR mode AES. This was discovered thanks to all of the new test cases added by Jussi Kivilinna. Signed-off-by: David S. Miller

sparc64: Fix unrolled AES 256-bit key loops.

2012-12-19T23:19:11Z

The basic scheme of the block mode assembler is that we start by enabling the FPU, loading the key into the floating point registers, then iterate calling the encrypt/decrypt routine for each block. For the 256-bit key cases, we run short on registers in the unrolled loops. So the {ENCRYPT,DECRYPT}_256_2() macros reload the key registers that get clobbered. The unrolled macros, {ENCRYPT,DECRYPT}_256(), are not mindful of this. So if we have a mix of multi-block and single-block calls, the single-block unrolled 256-bit encrypt/decrypt can run with some of the key registers clobbered. Handle this by always explicitly loading those registers before using the non-unrolled 256-bit macro. This was discovered thanks to all of the new test cases added by Jussi Kivilinna. Signed-off-by: David S. Miller

sparc64: Fix build with mix of modular vs. non-modular crypto drivers.

2012-11-10T04:55:16Z

We tried linking in a single built object to hold the device table, but only works if all of the sparc64 crypto modules get built the same way (modular vs. non-modular). Just include the device ID stub into each driver source file so that the table gets compiled into the correct result in all cases. Reported-by: Meelis Roos Signed-off-by: David S. Miller

sparc64: Fix function argument comment in camellia_sparc64_key_expand asm.

2012-09-21T19:04:51Z

Signed-off-by: David S. Miller