This is a note to let you know that I've just added the patch titled
crypto: marvell - Don't copy hash operation twice into the SRAM
to the 4.8-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
crypto-marvell-don-t-copy-hash-operation-twice-into-the-sram.patch
and it can be found in the queue-4.8 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 68c7f8c1c4e9b06e6b153fa3e9e0cda2ef5aaed8 Mon Sep 17 00:00:00 2001
From: Romain Perier <romain.perier@xxxxxxxxxxxxxxxxxx>
Date: Mon, 5 Dec 2016 09:56:38 +0100
Subject: crypto: marvell - Don't copy hash operation twice into the SRAM
From: Romain Perier <romain.perier@xxxxxxxxxxxxxxxxxx>
commit 68c7f8c1c4e9b06e6b153fa3e9e0cda2ef5aaed8 upstream.
No need to copy the template of an hash operation twice into the SRAM
from the step function.
Fixes: commit 85030c5168f1 ("crypto: marvell - Add support for chai...")
Signed-off-by: Romain Perier <romain.perier@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/crypto/marvell/hash.c | 3 ---
1 file changed, 3 deletions(-)
--- a/drivers/crypto/marvell/hash.c
+++ b/drivers/crypto/marvell/hash.c
@@ -172,9 +172,6 @@ static void mv_cesa_ahash_std_step(struc
for (i = 0; i < digsize / 4; i++)
writel_relaxed(creq->state[i], engine->regs + CESA_IVDIG(i));
- mv_cesa_adjust_op(engine, &creq->op_tmpl);
- memcpy_toio(engine->sram, &creq->op_tmpl, sizeof(creq->op_tmpl));
-
if (creq->cache_ptr)
memcpy_toio(engine->sram + CESA_SA_DATA_SRAM_OFFSET,
creq->cache, creq->cache_ptr);
Patches currently in stable-queue which might be from romain.perier@xxxxxxxxxxxxxxxxxx are
queue-4.8/crypto-marvell-don-t-corrupt-state-of-an-std-req-for-re-stepped-ahash.patch
queue-4.8/crypto-marvell-don-t-copy-hash-operation-twice-into-the-sram.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html