crypto: engine - Use crypto_request_complete

[ Upstream commit 6909823d47c17cba84e9244d04050b5db8d53789 ]

Use the crypto_request_complete helper instead of calling the
completion function directly.

Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Stable-dep-of: 4140aafcff16 ("crypto: engine - fix crypto_queue backlog handling")
Signed-off-by: Sasha Levin <sashal@kernel.org>

diff --git a/crypto/crypto_engine.c b/crypto/crypto_engine.c
index bb8e77077f020ce9b6ee9de194d47ad9e0258cc0..48c15f4079bb8b884cd9da23ed8bf2cd2d911116 100644 (file)
--- a/crypto/crypto_engine.c
+++ b/crypto/crypto_engine.c
@@ -54,7 +54,7 @@ static void crypto_finalize_request(struct crypto_engine *engine,
                }
        }
        lockdep_assert_in_softirq();
-       req->complete(req, err);
+       crypto_request_complete(req, err);
 
        kthread_queue_work(engine->kworker, &engine->pump_requests);
 }
@@ -130,7 +130,7 @@ start_request:
                engine->cur_req = async_req;
 
        if (backlog)
-               backlog->complete(backlog, -EINPROGRESS);
+               crypto_request_complete(backlog, -EINPROGRESS);
 
        if (engine->busy)
                was_busy = true;
@@ -214,7 +214,7 @@ req_err_1:
        }
 
 req_err_2:
-       async_req->complete(async_req, ret);
+       crypto_request_complete(async_req, ret);
 
 retry:
        /* If retry mechanism is supported, send new requests to engine */