From: sashiko-bot@kernel.org
To: "Koichiro Den" <den@valinux.co.jp>
Cc: vkoul@kernel.org, dmaengine@vger.kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v4 19/24] dmaengine: dw-edma: Drain LL entries for STOP and PAUSE
Date: Wed, 29 Jul 2026 14:56:56 +0000 [thread overview]
Message-ID: <20260729145656.B45351F00A3E@smtp.kernel.org> (raw)
In-Reply-To: <20260729143036.3087722-20-den@valinux.co.jp>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Infinite loop in dw_edma_wait_termination() leading to hung tasks if hardware stalls or is removed.
--
--- Patch [19]: [PATCH v4 19/24] dmaengine: dw-edma: Drain LL entries for STOP and PAUSE ---
commit 7c90dd7ea15ac01e52b8a14ed044dee1a6a2bfde
Author: Koichiro Den <den@valinux.co.jp>
Subject: dmaengine: dw-edma: Drain LL entries for STOP and PAUSE
This commit changes the channel termination process to wait for the
hardware to consume all published LL entries when a STOP or PAUSE is
requested, rather than discarding the ring state immediately.
> diff --git a/drivers/dma/dw-edma/dw-edma-core.c b/drivers/dma/dw-edma/dw-edma-core.c
> index b0e3f67d3942f..977392689205f 100644
> --- a/drivers/dma/dw-edma/dw-edma-core.c
> +++ b/drivers/dma/dw-edma/dw-edma-core.c
[ ... ]
> @@ -1590,18 +1638,21 @@ static void dw_edma_wait_termination(struct dma_chan *dchan)
> * A STOP may be deferred to a later interrupt while the channel is still
> * running. Wait until that handler completes the termination.
> */
> - while (time_before(jiffies, timeout)) {
> + for (;;) {
> scoped_guard(spinlock_irqsave, &chan->vc.lock)
> stopping = chan->request == EDMA_REQ_STOP;
>
> if (!stopping)
> return;
>
> + if (time_after_eq(jiffies, timeout)) {
> + dev_warn(chan->dw->chip->dev,
> + "timeout waiting for channel termination; still waiting\n");
> + timeout = jiffies + msecs_to_jiffies(5000);
> + }
> +
> fsleep(1000);
> }
[Severity: High]
Does this change introduce a potential infinite loop? By removing the absolute
timeout and converting this to an unbounded for (;;) loop, the function will
hang forever if the hardware stalls, drops an interrupt, or is
surprise-removed.
If chan->request never transitions away from EDMA_REQ_STOP (for example, if
dw->teardown is set and no further interrupts arrive),
dmaengine_terminate_sync() will block indefinitely. This could prevent driver
unbind, system suspend, or process exit.
Is there a fallback mechanism to eventually break out of this loop if the
hardware never recovers?
> -
> - dev_warn(chan->dw->chip->dev,
> - "timeout waiting for channel termination\n");
> }
>
> static void dw_edma_device_synchronize(struct dma_chan *dchan)
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729143036.3087722-1-den@valinux.co.jp?part=19
next prev parent reply other threads:[~2026-07-29 14:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 14:30 [PATCH v4 00/24] dmaengine: dw-edma: Support dynamic LL appends Koichiro Den
2026-07-29 14:30 ` [PATCH v4 01/24] dmaengine: dw-edma: Add dw_edma_core_ll_cur_idx() to get current LL entry index Koichiro Den
2026-07-29 14:54 ` sashiko-bot
2026-07-29 14:30 ` [PATCH v4 02/24] dmaengine: dw-edma: Add dw_edma_core_ll_clear() to clear LL control-word Koichiro Den
2026-07-29 14:30 ` [PATCH v4 03/24] dmaengine: dw-edma: Factor out linked-list transfer start Koichiro Den
2026-07-29 14:30 ` [PATCH v4 04/24] dmaengine: dw-edma: Make DMA link list work as a circular buffer Koichiro Den
2026-07-29 14:51 ` sashiko-bot
2026-07-29 14:30 ` [PATCH v4 05/24] dmaengine: dw-edma: Move callback result helper before LL helpers Koichiro Den
2026-07-29 14:30 ` [PATCH v4 06/24] dmaengine: dw-edma: Dispatch DONE interrupts by channel request Koichiro Den
2026-07-29 14:30 ` [PATCH v4 07/24] dmaengine: dw-edma: Centralize LL doorbell decisions Koichiro Den
2026-07-29 16:01 ` Frank Li
2026-07-29 14:30 ` [PATCH v4 08/24] dmaengine: dw-edma: Prepare LL progress event handling Koichiro Den
2026-07-29 16:04 ` Frank Li
2026-07-29 16:47 ` Frank Li
2026-07-30 1:27 ` Koichiro Den
2026-07-29 14:30 ` [PATCH v4 09/24] dmaengine: dw-edma: Prepare deferred IRQ reporting for LL events Koichiro Den
2026-07-29 14:30 ` [PATCH v4 10/24] dmaengine: dw-edma: Prepare LL kicks for event serialization Koichiro Den
2026-07-29 16:13 ` Frank Li
2026-07-29 14:30 ` [PATCH v4 11/24] dmaengine: dw-edma: Serialize LL event capture with channel kicks Koichiro Den
2026-07-29 14:51 ` sashiko-bot
2026-07-29 14:30 ` [PATCH v4 12/24] dmaengine: dw-edma: Keep channels stopped while ABORT is pending Koichiro Den
2026-07-29 14:30 ` [PATCH v4 13/24] dmaengine: dw-edma: Reclaim issued descriptors from IRQ-paired LL progress Koichiro Den
2026-07-29 14:30 ` [PATCH v4 14/24] dmaengine: dw-edma: Add LL interrupt placement policy Koichiro Den
2026-07-29 14:30 ` [PATCH v4 15/24] dmaengine: dw-edma: Recheck stopped LL channels before restart Koichiro Den
2026-07-29 14:46 ` sashiko-bot
2026-07-29 14:30 ` [PATCH v4 16/24] dmaengine: dw-edma: Use HDMA watermarks as progress events Koichiro Den
2026-07-29 14:30 ` [PATCH v4 17/24] dmaengine: dw-edma: Recover stopped channels from tx_status() Koichiro Den
2026-07-29 14:30 ` [PATCH v4 18/24] dmaengine: dw-edma: Make the LL ring reset a full channel resync Koichiro Den
2026-07-29 14:30 ` [PATCH v4 19/24] dmaengine: dw-edma: Drain LL entries for STOP and PAUSE Koichiro Den
2026-07-29 14:56 ` sashiko-bot [this message]
2026-07-29 14:30 ` [PATCH v4 20/24] dmaengine: dw-edma: Dynamically append requests while running Koichiro Den
2026-07-29 14:30 ` [PATCH v4 21/24] dmaengine: dw-edma: Add engine reset and enable operations Koichiro Den
2026-07-29 14:30 ` [PATCH v4 22/24] dmaengine: dw-edma: Add engine recovery infrastructure Koichiro Den
2026-07-29 15:02 ` sashiko-bot
2026-07-29 14:30 ` [PATCH v4 23/24] dmaengine: dw-edma: Detect and recover a stalled eDMA engine Koichiro Den
2026-07-29 14:30 ` [PATCH v4 24/24] dmaengine: dw-edma: Add trace support Koichiro Den
2026-07-29 14:55 ` sashiko-bot
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=20260729145656.B45351F00A3E@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=den@valinux.co.jp \
--cc=dmaengine@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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