mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.li@nxp.com>,
	Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH 2/6] dmaengine: plx_dma: fix descriptor ring leak in alloc_chan_resources()
Date: Fri, 6 Nov 2026 12:28:43 -0500	[thread overview]
Message-ID: <au4OSzBcNIzoS6zC@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20261103155202.461725-3-logang@deltatee.com>

On Tue, Nov 03, 2026 at 09:51:57AM -0600, Logan Gunthorpe wrote:
> If the device is removed between plx_dma_alloc_desc() and the pdev
> check, the error path frees hw_ring but leaks desc_ring and every
> descriptor in it.
>
> Add plx_dma_free_desc() and use it here and in
> plx_dma_free_chan_resources().
>
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Link: https://lore.kernel.org/dmaengine/20260717223217.B6FBF1F000E9@smtp.kernel.org
> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> ---
>  drivers/dma/plx_dma.c | 20 ++++++++++++++------
>  1 file changed, 14 insertions(+), 6 deletions(-)

Reviewed-by: Frank Li <Frank.Li@nxp.com>

>
> diff --git a/drivers/dma/plx_dma.c b/drivers/dma/plx_dma.c
> index 0a7ad2473cb1..bfccbb0c70e8 100644
> --- a/drivers/dma/plx_dma.c
> +++ b/drivers/dma/plx_dma.c
> @@ -404,6 +404,16 @@ static int plx_dma_alloc_desc(struct plx_dma_dev *plxdev)
>  	return -ENOMEM;
>  }
>
> +static void plx_dma_free_desc(struct plx_dma_dev *plxdev)
> +{
> +	int i;
> +
> +	for (i = 0; i < PLX_DMA_RING_COUNT; i++)
> +		kfree(plxdev->desc_ring[i]);
> +
> +	kfree(plxdev->desc_ring);
> +}
> +
>  static int plx_dma_alloc_chan_resources(struct dma_chan *chan)
>  {
>  	struct plx_dma_dev *plxdev = chan_to_plx_dma_dev(chan);
> @@ -424,7 +434,7 @@ static int plx_dma_alloc_chan_resources(struct dma_chan *chan)
>  	if (!rcu_dereference(plxdev->pdev)) {
>  		rcu_read_unlock();
>  		rc = -ENODEV;
> -		goto out_free_hw_ring;
> +		goto out_free_desc;
>  	}
>
>  	writel(PLX_REG_CTRL_RESET_VAL, plxdev->bar + PLX_REG_CTRL);
> @@ -443,6 +453,8 @@ static int plx_dma_alloc_chan_resources(struct dma_chan *chan)
>
>  	return PLX_DMA_RING_COUNT;
>
> +out_free_desc:
> +	plx_dma_free_desc(plxdev);
>  out_free_hw_ring:
>  	dma_free_coherent(plxdev->dma_dev.dev, ring_sz, plxdev->hw_ring,
>  			  plxdev->hw_ring_dma);
> @@ -454,7 +466,6 @@ static void plx_dma_free_chan_resources(struct dma_chan *chan)
>  	struct plx_dma_dev *plxdev = chan_to_plx_dma_dev(chan);
>  	size_t ring_sz = PLX_DMA_RING_COUNT * sizeof(*plxdev->hw_ring);
>  	int irq = -1;
> -	int i;
>
>  	spin_lock_bh(&plxdev->ring_lock);
>  	plxdev->ring_active = false;
> @@ -474,10 +485,7 @@ static void plx_dma_free_chan_resources(struct dma_chan *chan)
>
>  	plx_dma_abort_desc(plxdev);
>
> -	for (i = 0; i < PLX_DMA_RING_COUNT; i++)
> -		kfree(plxdev->desc_ring[i]);
> -
> -	kfree(plxdev->desc_ring);
> +	plx_dma_free_desc(plxdev);
>  	dma_free_coherent(plxdev->dma_dev.dev, ring_sz, plxdev->hw_ring,
>  			  plxdev->hw_ring_dma);
>
> --
> 2.47.3
>

  reply	other threads:[~2026-11-06 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 15:51 [PATCH 0/6] plx_dma fixes Logan Gunthorpe
2026-11-03 15:51 ` [PATCH 1/6] dmaengine: plx_dma: don't call pci_irq_vector() under rcu_read_lock() Logan Gunthorpe
2026-11-06 17:27   ` Frank Li
2026-11-03 15:51 ` [PATCH 2/6] dmaengine: plx_dma: fix descriptor ring leak in alloc_chan_resources() Logan Gunthorpe
2026-11-06 17:28   ` Frank Li [this message]
2026-11-03 15:51 ` [PATCH 3/6] dmaengine: plx_dma: use writel() for the 32-bit PLX_REG_CTRL register Logan Gunthorpe
2026-11-06 17:29   ` Frank Li
2026-11-03 15:51 ` [PATCH 4/6] dmaengine: plx_dma: add dma_rmb() after observing write-back status Logan Gunthorpe
2026-11-06 17:47   ` Frank Li
2026-11-06 23:13     ` Logan Gunthorpe
2026-11-03 15:52 ` [PATCH 5/6] dmaengine: plx_dma: use spin_lock_bh() in plx_dma_process_desc() Logan Gunthorpe
2026-11-06 17:48   ` Frank Li
2026-11-03 15:52 ` [PATCH 6/6] dmaengine: plx_dma: don't invoke client callbacks with ring_lock held Logan Gunthorpe

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=au4OSzBcNIzoS6zC@lizhi-Precision-Tower-5810 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.li@nxp.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=sashiko-bot@kernel.org \
    --cc=vkoul@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®