From: Rosen Penev <rosenp@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: Srujana Challa <schalla@marvell.com>,
Bharat Bhushan <bbhushan2@marvell.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] crypto: cesa: complete pending requests on device remove
Date: Wed, 16 Sep 2026 16:05:26 -0700 [thread overview]
Message-ID: <20260916230526.284982-1-rosenp@gmail.com> (raw)
mv_cesa_remove() unregisters the algorithms and frees the IRQs but never
drains the engine queues. Each engine can still hold outstanding requests
in three places: engine->req (currently in flight), engine->queue (queued
but not started), and engine->complete_queue (processed but not yet
reported). The latter two are only completed from the IRQ handler, which
is torn down before they are flushed.
If the device is unbound via sysfs while requests are outstanding, those
waiters never receive their completion callback and block indefinitely,
leaking the request and its scatterlist buffers.
Drain all three queues in mv_cesa_remove() and complete each remaining
request with -ENOENT before freeing the IRQ, so bound tasks are released.
Assisted-by: LLM
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
drivers/crypto/marvell/cesa/cesa.c | 46 ++++++++++++++++++++++++++++++
1 file changed, 46 insertions(+)
diff --git a/drivers/crypto/marvell/cesa/cesa.c b/drivers/crypto/marvell/cesa/cesa.c
index 564b09773507..25a30deca4c5 100644
--- a/drivers/crypto/marvell/cesa/cesa.c
+++ b/drivers/crypto/marvell/cesa/cesa.c
@@ -546,6 +546,52 @@ static void mv_cesa_remove(struct platform_device *pdev)
mv_cesa_remove_algs(cesa);
cesa_dev = NULL;
+
+ for (int i = 0; i < cesa->caps->nengines; i++) {
+ struct mv_cesa_engine *engine = &cesa->engines[i];
+ struct crypto_async_request *req;
+
+ /*
+ * Stop the engine before releasing resources so it no longer
+ * issues DMA to the SRAM region or to request scatterlists
+ * that are about to be unmapped.
+ */
+ writel(0, engine->regs + CESA_SA_INT_MSK);
+ writel(0, engine->regs + CESA_SA_CMD);
+ writel(0, engine->regs + CESA_TDMA_CONTROL);
+
+ spin_lock_bh(&engine->lock);
+ /*
+ * Complete the request currently in flight and drain the
+ * pending and already-processed queues with an error so that
+ * waiters do not block indefinitely when the device is unbound
+ * while requests are still outstanding.
+ */
+ if (engine->req) {
+ req = engine->req;
+ engine->req = NULL;
+ spin_unlock_bh(&engine->lock);
+ mv_cesa_complete_req(crypto_tfm_ctx(req->tfm), req,
+ -ENOENT);
+ spin_lock_bh(&engine->lock);
+ }
+
+ while ((req = crypto_dequeue_request(&engine->queue)) != NULL) {
+ spin_unlock_bh(&engine->lock);
+ mv_cesa_complete_req(crypto_tfm_ctx(req->tfm), req,
+ -ENOENT);
+ spin_lock_bh(&engine->lock);
+ }
+
+ while ((req = mv_cesa_engine_dequeue_complete_request(engine))
+ != NULL) {
+ spin_unlock_bh(&engine->lock);
+ mv_cesa_complete_req(crypto_tfm_ctx(req->tfm), req,
+ -ENOENT);
+ spin_lock_bh(&engine->lock);
+ }
+ spin_unlock_bh(&engine->lock);
+ }
}
static const struct platform_device_id mv_cesa_plat_id_table[] = {
--
2.55.0
reply other threads:[~2026-09-16 23:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260916230526.284982-1-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schalla@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®