linux-stable/drivers/crypto/marvell
Romain Perier 9e5f7a149e crypto: marvell - Don't corrupt state of an STD req for re-stepped ahash
mv_cesa_hash_std_step() copies the creq->state into the SRAM at each
step, but this is only required on the first one. By doing that, we
overwrite the engine state, and get erroneous results when the crypto
request is split in several chunks to fit in the internal SRAM.

This commit changes the function to copy the state only on the first
step.

Fixes: commit 2786cee8e5 ("crypto: marvell - Move SRAM I/O op...")
Signed-off-by: Romain Perier <romain.perier@free-electrons.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2016-12-07 19:55:17 +08:00
..
cesa.c crypto: marvell - Update transformation context for each dequeued req 2016-08-09 18:47:30 +08:00
cesa.h crypto: marvell - Add support for chaining crypto requests in TDMA mode 2016-06-23 18:29:51 +08:00
cipher.c crypto: marvell - Don't copy IV vectors from the _process op for ciphers 2016-07-29 18:30:17 +08:00
hash.c crypto: marvell - Don't corrupt state of an STD req for re-stepped ahash 2016-12-07 19:55:17 +08:00
Makefile
tdma.c crypto: marvell - be explicit about destination in mv_cesa_dma_add_op() 2016-08-09 18:47:29 +08:00