test_aead_speed is written for sync algorithms without specifically
requiring them. The effect is that an async algorithm may be used without
setting up the request callback, this leading to a kernel panic.
Signed-off-by: Cristian Stoica <cristian.sto...@freescale.com>
---
crypto/tcrypt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
index 4b9e23f..5dc5a25 100644
--- a/crypto/tcrypt.c
+++ b/crypto/tcrypt.c
@@ -314,7 +314,8 @@ static void test_aead_speed(const char *algo, int enc,
unsigned int secs,
asg = &sg[8];
sgout = &asg[8];
- tfm = crypto_alloc_aead(algo, 0, 0);
+ /* This test is not for ASYNC algorithms */
+ tfm = crypto_alloc_aead(algo, 0, CRYPTO_ALG_ASYNC);
if (IS_ERR(tfm)) {
pr_err("alg: aead: Failed to load transform for %s: %ld\n",
algo,
--
2.0.5
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
