Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Slavin Liu <bolin.liu@seu.edu.cn>
Cc: vkoul@kernel.org, Frank.Li@kernel.org, wens@kernel.org,
	jernej.skrabec@gmail.com, samuel@sholland.org,
	dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dmaengine: sun6i: Fix use-after-free in slave sg LLI error cleanup
Date: Wed, 30 Sep 2026 15:42:06 -0400	[thread overview]
Message-ID: <ar1mDmkjSgs934sk@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20260927003951.11210-1-bolin.liu@seu.edu.cn>

On Sun, Sep 27, 2026 at 08:39:50AM +0800, Slavin Liu wrote:
> sun6i_dma_prep_slave_sg() chains one pool-allocated LLI per
> scatterlist entry.  When a later dma_pool_alloc() fails (GFP_NOWAIT,
> so it does not wait for reclaim, making failure realistic under memory
> pressure), the err_lli_free path walks the chain to free what was
> built: the loop body hands the current LLI back to the pool with
> dma_pool_free(), and the for-loop increment then reads
> v_lli->p_lli_next and v_lli->v_lli_next from the memory that was just
> freed and may already have been reallocated.
>
> Cache both next fields of the current LLI before freeing it.
>
> Fixes: 4fbd804e009a ("dmaengine: sun6i: Fix memory leaks")
> Assisted-by: LLM
> Signed-off-by: Slavin Liu <bolin.liu@seu.edu.cn>
> ---

similar patch already in next branch

https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git/commit/?id=f472919f4c0650d7fb22bb230eacaada0c6ee951

Frank

>  drivers/dma/sun6i-dma.c | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
> index 7704b016aed8..025a43d0298d 100644
> --- a/drivers/dma/sun6i-dma.c
> +++ b/drivers/dma/sun6i-dma.c
> @@ -790,9 +790,14 @@ static struct dma_async_tx_descriptor *sun6i_dma_prep_slave_sg(
>  	return vchan_tx_prep(&vchan->vc, &txd->vd, flags);
>
>  err_lli_free:
> -	for (p_lli = txd->p_lli, v_lli = txd->v_lli; v_lli;
> -	     p_lli = v_lli->p_lli_next, v_lli = v_lli->v_lli_next)
> +	for (p_lli = txd->p_lli, v_lli = txd->v_lli; v_lli;) {
> +		dma_addr_t next_p_lli = v_lli->p_lli_next;
> +		struct sun6i_dma_lli *next_v_lli = v_lli->v_lli_next;
> +
>  		dma_pool_free(sdev->pool, v_lli, p_lli);
> +		p_lli = next_p_lli;
> +		v_lli = next_v_lli;
> +	}
>  	kfree(txd);
>  	return NULL;
>  }
> --
> 2.34.1
>


      parent reply	other threads:[~2026-09-30 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  0:39 [PATCH 1/2] dmaengine: sun6i: Fix use-after-free in slave sg LLI error cleanup Slavin Liu
2026-09-27  0:39 ` [PATCH 2/2] dmaengine: sun6i: Fix use-after-free in cyclic " Slavin Liu
2026-09-30 19:42 ` Frank Li [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=ar1mDmkjSgs934sk@lizhi-Precision-Tower-5810 \
    --to=frank.li@oss.nxp.com \
    --cc=Frank.Li@kernel.org \
    --cc=bolin.liu@seu.edu.cn \
    --cc=dmaengine@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=samuel@sholland.org \
    --cc=vkoul@kernel.org \
    --cc=wens@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