From: Frank Li <Frank.li@oss.nxp.com>
To: Chaithanya Lagisetty <nagachaithanya9911@gmail.com>
Cc: Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, Frank Li <Frank.Li@kernel.org>,
Chen-Yu Tsai <wens@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Maxime Ripard <mripard@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: sun6i: fix use-after-free in descriptor error path
Date: Fri, 14 Aug 2026 17:00:21 -0400 [thread overview]
Message-ID: <an-B5SdpGfsJoudH@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <an9nNnRMAzhHcjlS@lizhi-Precision-Tower-5810>
On Fri, Aug 14, 2026 at 03:06:30PM -0400, Frank Li wrote:
> On Mon, Aug 10, 2026 at 10:20:44AM +0000, Chaithanya Lagisetty wrote:
> > The err_lli_free cleanup loops in sun6i_dma_prep_slave_sg() and
> > sun6i_dma_prep_dma_cyclic() free each LLI node with dma_pool_free()
> > and then dereference the freed node to obtain v_lli_next and
> > p_lli_next for the next loop iteration.
> >
> > Save the next pointers before freeing, matching the pattern already used
> > in sun6i_dma_free_desc().
> >
> > Fixes: 9aa48806edb8 ("dmaengine: sun6i: Do not use virt_to_phys")
> > Signed-off-by: Chaithanya Lagisetty <nagachaithanya9911@gmail.com>
> > ---
>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
Drop review-by, I prefer use below method to fix
https://patchwork.kernel.org/project/linux-dmaengine/patch/20260727061142.44195-1-zenghongling@kylinos.cn/
Frank
>
> > drivers/dma/sun6i-dma.c | 18 ++++++++++++------
> > 1 file changed, 12 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
> > index f47a326dd7ff..2439fa6564f2 100644
> > --- a/drivers/dma/sun6i-dma.c
> > +++ b/drivers/dma/sun6i-dma.c
> > @@ -720,10 +720,10 @@ static struct dma_async_tx_descriptor *sun6i_dma_prep_slave_sg(
> > struct sun6i_dma_dev *sdev = to_sun6i_dma_dev(chan->device);
> > struct sun6i_vchan *vchan = to_sun6i_vchan(chan);
> > struct dma_slave_config *sconfig = &vchan->cfg;
> > - struct sun6i_dma_lli *v_lli, *prev = NULL;
> > + struct sun6i_dma_lli *v_lli, *v_next, *prev = NULL;
> > struct sun6i_desc *txd;
> > struct scatterlist *sg;
> > - dma_addr_t p_lli;
> > + dma_addr_t p_lli, p_next;
> > u32 lli_cfg;
> > int i, ret;
> >
> > @@ -789,8 +789,11 @@ static struct dma_async_tx_descriptor *sun6i_dma_prep_slave_sg(
> >
> > 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)
> > + p_lli = p_next, v_lli = v_next) {
> > + v_next = v_lli->v_lli_next;
> > + p_next = v_lli->p_lli_next;
> > dma_pool_free(sdev->pool, v_lli, p_lli);
> > + }
> > kfree(txd);
> > return NULL;
> > }
> > @@ -806,9 +809,9 @@ static struct dma_async_tx_descriptor *sun6i_dma_prep_dma_cyclic(
> > struct sun6i_dma_dev *sdev = to_sun6i_dma_dev(chan->device);
> > struct sun6i_vchan *vchan = to_sun6i_vchan(chan);
> > struct dma_slave_config *sconfig = &vchan->cfg;
> > - struct sun6i_dma_lli *v_lli, *prev = NULL;
> > + struct sun6i_dma_lli *v_lli, *v_next, *prev = NULL;
> > struct sun6i_desc *txd;
> > - dma_addr_t p_lli;
> > + dma_addr_t p_lli, p_next;
> > u32 lli_cfg;
> > unsigned int i, periods = buf_len / period_len;
> > int ret;
> > @@ -870,8 +873,11 @@ static struct dma_async_tx_descriptor *sun6i_dma_prep_dma_cyclic(
> >
> > 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)
> > + p_lli = p_next, v_lli = v_next) {
> > + v_next = v_lli->v_lli_next;
> > + p_next = v_lli->p_lli_next;
> > dma_pool_free(sdev->pool, v_lli, p_lli);
> > + }
> > kfree(txd);
> > return NULL;
> > }
> > --
> > 2.43.0
> >
next prev parent reply other threads:[~2026-08-14 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 10:20 Chaithanya Lagisetty
2026-08-14 19:06 ` Frank Li
2026-08-14 21:00 ` Frank Li [this message]
2026-08-15 7:24 ` Chaithanya Lagisetty
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=an-B5SdpGfsJoudH@lizhi-Precision-Tower-5810 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--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=mripard@kernel.org \
--cc=nagachaithanya9911@gmail.com \
--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
all inboxes | Powered by JetHome®