crypto: inside-secure - move hash result dma mapping to request
In heavy traffic the DMA mapping is overwritten by multiple requests as
the DMA address is stored in a global context. This patch moves this
information to the per-hash request context so that it can't be
overwritten.
Fixes: 1b44c5a60c
("crypto: inside-secure - add SafeXcel EIP197 crypto engine driver")
Signed-off-by: Ofer Heifetz <oferh@marvell.com>
[Antoine: rebased the patch, small fixes, commit message.]
Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
This commit is contained in:
@@ -538,15 +538,10 @@ finalize:
|
||||
}
|
||||
|
||||
void safexcel_free_context(struct safexcel_crypto_priv *priv,
|
||||
struct crypto_async_request *req,
|
||||
int result_sz)
|
||||
struct crypto_async_request *req)
|
||||
{
|
||||
struct safexcel_context *ctx = crypto_tfm_ctx(req->tfm);
|
||||
|
||||
if (ctx->result_dma)
|
||||
dma_unmap_single(priv->dev, ctx->result_dma, result_sz,
|
||||
DMA_FROM_DEVICE);
|
||||
|
||||
if (ctx->cache) {
|
||||
dma_unmap_single(priv->dev, ctx->cache_dma, ctx->cache_sz,
|
||||
DMA_TO_DEVICE);
|
||||
|
Reference in New Issue
Block a user