All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: Samarth Narang <samarth.colleges@gmail.com>
Cc: Han Xu <han.xu@nxp.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Richard Weinberger <richard@nod.at>,
	imx@lists.linux.dev, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: gpmi: terminate the DMA chain on completion timeout
Date: Fri, 30 Oct 2026 09:56:46 -0500	[thread overview]
Message-ID: <auSwLrB2ewr2j-c2@SMW015318> (raw)
In-Reply-To: <20261030143945.2923554-1-samarth.colleges@gmail.com>

On Fri, Oct 30, 2026 at 02:39:45PM +0000, Samarth Narang wrote:
> [You don't often get email from samarth.colleges@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> When DMA completion times out in gpmi_nfc_exec_op(), the driver unmaps
> the operation's buffers and returns -ETIMEDOUT without stopping the APBH
> DMA channel. Since mxs-dma leaves the channel in DMA_IN_PROGRESS, the
> pending descriptor chain may resume after the timeout, while a
> subsequent operation can append new descriptors to the stale chain and
> cause the old DATA_IN transfer to execute again against an unmapped
> buffer.
>
> This can result in DMA writes to memory that has already been released,
> including buffers freed after ONFI parameter page detection in
> nand_onfi_detect().
>
> Terminate the channel with dmaengine_terminate_sync() before unmapping
> so that outstanding transfers are stopped and subsequent operations
> begin with a fresh descriptor chain.
>
> Fixes: ef347c0cfd61 ("mtd: rawnand: gpmi: Implement exec_op")
> Assisted-by: LLM
> Signed-off-by: Samarth Narang <samarth.colleges@gmail.com>
> ---

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

> This issue was identified by a research static analyzer for DMA
> lifecycle ordering and has not been validated on hardware.
> Compile-tested only.
>
>  drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c |    2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> index 527165ccc..a8106de2c 100644
> --- a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> @@ -2659,6 +2659,8 @@ static int gpmi_nfc_exec_op(struct nand_chip *chip,
>         if (!to) {
>                 dev_err(this->dev, "DMA timeout, last DMA\n");
>                 gpmi_dump_info(this);
> +               /* Retire the APBH chain before its buffers are unmapped. */
> +               dmaengine_terminate_sync(get_dma_chan(this));
>                 ret = -ETIMEDOUT;
>                 goto unmap;
>         }
>
> base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907
>

WARNING: multiple messages have this Message-ID (diff)
From: Frank Li <Frank.li@oss.nxp.com>
To: Samarth Narang <samarth.colleges@gmail.com>
Cc: Han Xu <han.xu@nxp.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Richard Weinberger <richard@nod.at>,
	imx@lists.linux.dev, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: rawnand: gpmi: terminate the DMA chain on completion timeout
Date: Fri, 30 Oct 2026 09:56:46 -0500	[thread overview]
Message-ID: <auSwLrB2ewr2j-c2@SMW015318> (raw)
In-Reply-To: <20261030143945.2923554-1-samarth.colleges@gmail.com>

On Fri, Oct 30, 2026 at 02:39:45PM +0000, Samarth Narang wrote:
> [You don't often get email from samarth.colleges@gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> When DMA completion times out in gpmi_nfc_exec_op(), the driver unmaps
> the operation's buffers and returns -ETIMEDOUT without stopping the APBH
> DMA channel. Since mxs-dma leaves the channel in DMA_IN_PROGRESS, the
> pending descriptor chain may resume after the timeout, while a
> subsequent operation can append new descriptors to the stale chain and
> cause the old DATA_IN transfer to execute again against an unmapped
> buffer.
>
> This can result in DMA writes to memory that has already been released,
> including buffers freed after ONFI parameter page detection in
> nand_onfi_detect().
>
> Terminate the channel with dmaengine_terminate_sync() before unmapping
> so that outstanding transfers are stopped and subsequent operations
> begin with a fresh descriptor chain.
>
> Fixes: ef347c0cfd61 ("mtd: rawnand: gpmi: Implement exec_op")
> Assisted-by: LLM
> Signed-off-by: Samarth Narang <samarth.colleges@gmail.com>
> ---

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

> This issue was identified by a research static analyzer for DMA
> lifecycle ordering and has not been validated on hardware.
> Compile-tested only.
>
>  drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c |    2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> index 527165ccc..a8106de2c 100644
> --- a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> @@ -2659,6 +2659,8 @@ static int gpmi_nfc_exec_op(struct nand_chip *chip,
>         if (!to) {
>                 dev_err(this->dev, "DMA timeout, last DMA\n");
>                 gpmi_dump_info(this);
> +               /* Retire the APBH chain before its buffers are unmapped. */
> +               dmaengine_terminate_sync(get_dma_chan(this));
>                 ret = -ETIMEDOUT;
>                 goto unmap;
>         }
>
> base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907
>

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2026-10-30 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 14:39 [PATCH] mtd: rawnand: gpmi: terminate the DMA chain on completion timeout Samarth Narang
2026-10-30 14:39 ` Samarth Narang
2026-10-30 14:56 ` Frank Li [this message]
2026-10-30 14:56   ` Frank Li
2026-10-30 15:00 ` Miquel Raynal
2026-10-30 15:00   ` Miquel Raynal

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=auSwLrB2ewr2j-c2@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=han.xu@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=samarth.colleges@gmail.com \
    --cc=vigneshr@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.