Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hari Prasath <gehariprasath@ti.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>, Nishanth Menon <nm@ti.com>,
	"Santosh Shilimkar" <ssantosh@kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: ti: knav_dma: remove debugfs file on teardown
Date: Tue, 30 Jun 2026 16:15:09 +0530	[thread overview]
Message-ID: <b47cd486-5f64-41b4-9cf1-2f6bbad523c9@ti.com> (raw)
In-Reply-To: <20260615091200.2373-1-pengpeng@iscas.ac.cn>

Hello,

On 15/06/26 2:42 pm, Pengpeng Hou wrote:
> knav_dma_probe() creates the global knav_dma debugfs file whose show
> callback walks the global kdev list. knav_dma_remove() tears down the DMA
> instances and runtime PM but leaves that debugfs file and global ready
> state behind.
> 
> Save the debugfs dentry, remove it before destroying the DMA state, and
> clear the global ready pointer state during remove.
> 
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
>   drivers/soc/ti/knav_dma.c | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/soc/ti/knav_dma.c b/drivers/soc/ti/knav_dma.c
> index e5f5e3142fc4..9277c525ac21 100644
> --- a/drivers/soc/ti/knav_dma.c
> +++ b/drivers/soc/ti/knav_dma.c
> @@ -125,6 +125,7 @@ struct knav_dma_chan {
>   			ch->channel : ch->flow)
>   
>   static struct knav_dma_pool_device *kdev;
> +static struct dentry *knav_dma_debugfs;
>   
>   static bool device_ready;
>   bool knav_dma_device_ready(void)
> @@ -740,8 +741,9 @@ static int knav_dma_probe(struct platform_device *pdev)
>   		goto err_put_sync;
>   	}
>   
> -	debugfs_create_file("knav_dma", S_IFREG | S_IRUGO, NULL, NULL,
> -			    &knav_dma_debug_fops);
> +	knav_dma_debugfs = debugfs_create_file("knav_dma", 0444,
> +					       NULL, NULL,
> +					       &knav_dma_debug_fops);
>   
>   	device_ready = true;
>   	return ret;
> @@ -758,6 +760,10 @@ static void knav_dma_remove(struct platform_device *pdev)
>   {
>   	struct knav_dma_device *dma;
>   
> +	device_ready = false;
> +	debugfs_remove(knav_dma_debugfs);

Does this handle the case where a process already has the debugfs file 
open? A concurrent read() from the userspace could still potentially 
reach knav_dma_debug_show() and access kdev while it's being torn down
below. Pls check and add necessary protection around kdev access.

Regards,
Hari 


> +	knav_dma_debugfs = NULL;
> +
>   	list_for_each_entry(dma, &kdev->list, list) {
>   		if (atomic_dec_return(&dma->ref_count) == 0)
>   			knav_dma_hw_destroy(dma);
> @@ -765,6 +771,7 @@ static void knav_dma_remove(struct platform_device *pdev)
>   
>   	pm_runtime_put_sync(&pdev->dev);
>   	pm_runtime_disable(&pdev->dev);
> +	kdev = NULL;
>   }
>   
>   static struct of_device_id of_match[] = {



      parent reply	other threads:[~2026-06-30 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15  9:12 [PATCH] soc: ti: knav_dma: remove debugfs file on teardown Pengpeng Hou
2026-06-29 16:54 ` Nishanth Menon
2026-06-30 10:45 ` Hari Prasath [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=b47cd486-5f64-41b4-9cf1-2f6bbad523c9@ti.com \
    --to=gehariprasath@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=pengpeng@iscas.ac.cn \
    --cc=ssantosh@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