summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorTero Kristo <t-kristo@ti.com>2019-11-05 17:00:59 +0300
committerHerbert Xu <herbert@gondor.apana.org.au>2019-12-11 11:36:58 +0300
commit6585cd3683c624d9cbe5cbc480f870b2d1df47db (patch)
tree300dff35717c646b9f87098765f69e5dcefb0a49 /drivers
parent60a0894c323af7de0a1b69d64f7d81d13dd9b16c (diff)
downloadlinux-6585cd3683c624d9cbe5cbc480f870b2d1df47db.tar.xz
crypto: omap-aes - fixup aligned data cleanup
Aligned data cleanup is using wrong pointers in the cleanup calls. Most of the time these are right, but can cause mysterious problems in some cases. Fix to use the same pointers that were used with the align call. Signed-off-by: Tero Kristo <t-kristo@ti.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/crypto/omap-aes.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c
index e3f2ed0184f8..de05b35283bf 100644
--- a/drivers/crypto/omap-aes.c
+++ b/drivers/crypto/omap-aes.c
@@ -502,10 +502,10 @@ static void omap_aes_done_task(unsigned long data)
omap_aes_crypt_dma_stop(dd);
}
- omap_crypto_cleanup(dd->in_sgl, NULL, 0, dd->total_save,
+ omap_crypto_cleanup(dd->in_sg, NULL, 0, dd->total_save,
FLAGS_IN_DATA_ST_SHIFT, dd->flags);
- omap_crypto_cleanup(&dd->out_sgl, dd->orig_out, 0, dd->total_save,
+ omap_crypto_cleanup(dd->out_sg, dd->orig_out, 0, dd->total_save,
FLAGS_OUT_DATA_ST_SHIFT, dd->flags);
/* Update IV output */