From: Rosen Penev <rosenp@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: Christian Marangi <ansuelsmth@gmail.com>,
Antoine Tenart <atenart@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] crypto: eip93: fix IRQ teardown ordering in remove path
Date: Wed, 9 Sep 2026 14:12:18 -0700 [thread overview]
Message-ID: <20260909211218.15388-1-rosenp@gmail.com> (raw)
Switch from devm_request_threaded_irq() to request_threaded_irq() so
that free_irq() can be called at the correct position in the remove
path. Move the IRQ registration after tasklet_init() in probe to
ensure the tasklet is ready before the handler can fire.
Reorder eip93_cleanup() to:
1. disable device interrupts (HW)
2. free_irq() - synchronizes and removes the handler
3. tasklet_kill() - safe, no new IRQs can arrive
The previous order (tasklet_kill before interrupt disable) could race:
an IRQ arriving after tasklet_kill() would schedule the already-killed
tasklet. With devm_request_threaded_irq(), free_irq() ran after the
remove callback returned, leaving the handler registered while device
state was being torn down.
Assisted-by: opencode:big-pickle
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
.../crypto/inside-secure/eip93/eip93-main.c | 27 ++++++++++++-------
1 file changed, 18 insertions(+), 9 deletions(-)
diff --git a/drivers/crypto/inside-secure/eip93/eip93-main.c b/drivers/crypto/inside-secure/eip93/eip93-main.c
index e62785952b0d..4cfddfd1935b 100644
--- a/drivers/crypto/inside-secure/eip93/eip93-main.c
+++ b/drivers/crypto/inside-secure/eip93/eip93-main.c
@@ -395,12 +395,16 @@ static int eip93_desc_init(struct eip93_device *eip93)
static void eip93_cleanup(struct eip93_device *eip93)
{
- tasklet_kill(&eip93->ring->done_task);
-
- /* Clear/ack all interrupts before disable all */
+ /* Stop HW from asserting IRQ first */
eip93_irq_clear(eip93, EIP93_INT_ALL);
eip93_irq_disable(eip93, EIP93_INT_ALL);
+ /* Synchronize and unregister the IRQ handler */
+ free_irq(eip93->irq, eip93);
+
+ /* No new IRQs can arrive - safe to kill the tasklet */
+ tasklet_kill(&eip93->ring->done_task);
+
writel(0, eip93->base + EIP93_REG_PE_CLOCK_CTRL);
eip93_desc_free(eip93);
@@ -430,12 +434,6 @@ static int eip93_crypto_probe(struct platform_device *pdev)
if (eip93->irq < 0)
return eip93->irq;
- ret = devm_request_threaded_irq(eip93->dev, eip93->irq, eip93_irq_handler,
- NULL, IRQF_ONESHOT,
- dev_name(eip93->dev), eip93);
- if (ret)
- return ret;
-
ret = eip93_desc_init(eip93);
if (ret)
return ret;
@@ -448,6 +446,11 @@ static int eip93_crypto_probe(struct platform_device *pdev)
spin_lock_init(&eip93->ring->idr_lock);
idr_init(&eip93->ring->crypto_async_idr);
+ ret = request_threaded_irq(eip93->irq, eip93_irq_handler, NULL,
+ IRQF_ONESHOT, dev_name(eip93->dev), eip93);
+ if (ret)
+ goto err_free_tasklet;
+
algo_flags = readl(eip93->base + EIP93_REG_PE_OPTION_1);
eip93_initialize(eip93, algo_flags);
@@ -472,6 +475,12 @@ static int eip93_crypto_probe(struct platform_device *pdev)
readl(eip93->base + EIP93_REG_PE_OPTION_0));
return 0;
+
+err_free_tasklet:
+ idr_destroy(&eip93->ring->crypto_async_idr);
+ tasklet_kill(&eip93->ring->done_task);
+ eip93_desc_free(eip93);
+ return ret;
}
static void eip93_crypto_remove(struct platform_device *pdev)
--
2.55.0
reply other threads:[~2026-09-09 21:12 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=20260909211218.15388-1-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=ansuelsmth@gmail.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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