On Fri, 2013-08-02 at 15:58 -0500, Fionnuala Gunter wrote:
The chaining value from co-processor was not being saved. This value is
needed because it is used as the IV, for example by cts i.e.
cts(cbc(aes)).
Signed-off-by: Fionnuala Gunter <redacted>
Signed-off-by: Marcelo Cerri <redacted>
So now you guys are sending the patch to linuxppc-dev and not the crypto
list ..
I need to understand things better here. Any reason why those drivers
aren't handled by the crypto maintainer ?
Ben.
quoted hunk ↗ jump to hunk
---
drivers/crypto/nx/nx-aes-cbc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/crypto/nx/nx-aes-cbc.c
b/drivers/crypto/nx/nx-aes-cbc.c
index 35d483f..a2f99a9 100644
--- a/drivers/crypto/nx/nx-aes-cbc.c
+++ b/drivers/crypto/nx/nx-aes-cbc.c
@@ -95,6 +95,7 @@ static int cbc_aes_nx_crypt(struct blkcipher_desc
*desc,
if (rc)
goto out;
+ memcpy(desc->info, csbcpb->cpb.aes_cbc.cv, AES_BLOCK_SIZE);
atomic_inc(&(nx_ctx->stats->aes_ops));
atomic64_add(csbcpb->csb.processed_byte_count,
&(nx_ctx->stats->aes_bytes));