From: Tom Lendacky <thomas.lendacky@amd.com>
To: Koba Ko <koba.ko@canonical.com>, John Allen <john.allen@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: crypto: ccp - Release dma channels before dmaengine unrgister
Date: Tue, 30 Aug 2022 10:32:46 -0500 [thread overview]
Message-ID: <c3ea3992-df42-3a26-6d30-834368faf91c@amd.com> (raw)
In-Reply-To: <20220830093439.951960-1-koba.ko@canonical.com>
On 8/30/22 04:34, Koba Ko wrote:
> A warning is shown during shutdown,
>
> __dma_async_device_channel_unregister called while 2 clients hold a reference
> WARNING: CPU: 15 PID: 1 at drivers/dma/dmaengine.c:1110
> __dma_async_device_channel_unregister
>
> Call dma_release_channel for occupied channles
> before dma_async_device_unregister.
>
> Fixes: 4cbe9bc34ed0 ("crypto: ccp - ccp_dmaengine_unregister release dma channels")
> Signed-off-by: Koba Ko <koba.ko@canonical.com>
> ---
> drivers/crypto/ccp/ccp-dmaengine.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/ccp/ccp-dmaengine.c b/drivers/crypto/ccp/ccp-dmaengine.c
> index 7d4b4ad1db1f3..ba3eb1ac3b55d 100644
> --- a/drivers/crypto/ccp/ccp-dmaengine.c
> +++ b/drivers/crypto/ccp/ccp-dmaengine.c
> @@ -641,6 +641,10 @@ static void ccp_dma_release(struct ccp_device *ccp)
> for (i = 0; i < ccp->cmd_q_count; i++) {
> chan = ccp->ccp_dma_chan + i;
> dma_chan = &chan->dma_chan;
> +
> + if (dma_chan->client_count)
> + dma_release_channel(dma_chan);
> +
> tasklet_kill(&chan->cleanup_tasklet);
> list_del_rcu(&dma_chan->device_node);
> }
> @@ -762,12 +766,14 @@ int ccp_dmaengine_register(struct ccp_device *ccp)
> void ccp_dmaengine_unregister(struct ccp_device *ccp)
> {
> struct dma_device *dma_dev = &ccp->dma_dev;
> + struct dma_chan *dma_chan;
> + unsigned int i;
>
> if (!dmaengine)
> return;
>
> - dma_async_device_unregister(dma_dev);
> ccp_dma_release(ccp);
> + dma_async_device_unregister(dma_dev);
Seems the right way to get rid of the warn, but can there still be a race
where the channel is grabbed again after ccp_dma_release() and before
dma_async_device_unregister() is called?
Thanks,
Tom
>
> kmem_cache_destroy(ccp->dma_desc_cache);
> kmem_cache_destroy(ccp->dma_cmd_cache);
next prev parent reply other threads:[~2022-08-30 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 9:34 Koba Ko
2022-08-30 15:32 ` Tom Lendacky [this message]
2022-08-31 5:39 ` Koba Ko
2022-08-31 12:54 ` Tom Lendacky
2022-08-31 1:03 ` kernel test robot
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=c3ea3992-df42-3a26-6d30-834368faf91c@amd.com \
--to=thomas.lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=koba.ko@canonical.com \
--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
all inboxes | Powered by JetHome®