Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "jiale yao" <19888972804@163.com>
To: "Tom Lendacky" <thomas.lendacky@amd.com>,
	"John Allen" <john.allen@amd.com>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	"Gary R Hook" <gary.hook@amd.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re:[PATCH] crypto: ccp: drain v5 IRQ tasklet during teardown
Date: Thu, 24 Sep 2026 17:19:35 +0800 (CST)	[thread overview]
Message-ID: <6bd9f4f5.88e0.1a0d2b6924b.Coremail.19888972804@163.com> (raw)
In-Reply-To: <20260924090537.173532-1-yaojiale02@163.com>

Patched in https://lore.kernel.org/all/arOUsmw2dweuSVzq@gondor.apana.org.au/
ignore this, sorry.



At 2026-09-24 17:05:37, "Jiale Yao" <yaojiale02@163.com> wrote:
>On PCI devices using MSI-X, ccp5_irq_handler() disables the queue
>interrupts and schedules ccp->irq_tasklet. The tasklet calls
>ccp5_irq_bh(), which accesses registers and wait queues through
>ccp->cmd_q.
>
>Both the ccp5_init() error path and ccp5_destroy() free the CCP IRQ
>before the command queues and the device-managed ccp allocation are
>released. sp_free_ccp_irq() prevents another hard IRQ and waits for an
>in-flight handler, but it does not drain a tasklet that the handler
>already scheduled. The tasklet can therefore access ccp->cmd_q after
>its backing allocation has been released.
>
>Kill the tasklet after sp_free_ccp_irq(), when no handler can schedule
>it again, and before the command queues or ccp can be released. Check
>ccp->use_tasklet because the tasklet is initialized only for MSI-X.
>
>Fixes: 6263b51eb319 ("crypto: ccp - Change ISR handler method for a v5 CCP")
>Cc: stable@vger.kernel.org
>Signed-off-by: Jiale Yao <yaojiale02@163.com>
>---
> drivers/crypto/ccp/ccp-dev-v5.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
>diff --git a/drivers/crypto/ccp/ccp-dev-v5.c b/drivers/crypto/ccp/ccp-dev-v5.c
>index dcd6aab51e47..dacde9614e8a 100644
>--- a/drivers/crypto/ccp/ccp-dev-v5.c
>+++ b/drivers/crypto/ccp/ccp-dev-v5.c
>@@ -995,6 +995,8 @@ static int ccp5_init(struct ccp_device *ccp)
> 
> e_irq:
> 	sp_free_ccp_irq(ccp->sp, ccp);
>+	if (ccp->use_tasklet)
>+		tasklet_kill(&ccp->irq_tasklet);
> 
> e_pool:
> 	for (i = 0; i < ccp->cmd_q_count; i++)
>@@ -1046,6 +1048,8 @@ static void ccp5_destroy(struct ccp_device *ccp)
> 			kthread_stop(ccp->cmd_q[i].kthread);
> 
> 	sp_free_ccp_irq(ccp->sp, ccp);
>+	if (ccp->use_tasklet)
>+		tasklet_kill(&ccp->irq_tasklet);
> 
> 	/* Flush the cmd and backlog queue */
> 	while (!list_empty(&ccp->cmd)) {
>-- 
>2.34.1

      reply	other threads:[~2026-09-24  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  9:05 [PATCH] crypto: ccp: drain v5 IRQ tasklet during teardown Jiale Yao
2026-09-24  9:19 ` jiale yao [this message]

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=6bd9f4f5.88e0.1a0d2b6924b.Coremail.19888972804@163.com \
    --to=19888972804@163.com \
    --cc=davem@davemloft.net \
    --cc=gary.hook@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=john.allen@amd.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=thomas.lendacky@amd.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