From: Frank Li <Frank.li@oss.nxp.com>
To: Cosmin Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Seraj Alijan <seraj.alijan@sondrel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: dmatest: fix race between wait for thread and thread start
Date: Mon, 12 Oct 2026 09:56:09 -0500 [thread overview]
Message-ID: <asz1CVWrS7zst1rE@SMW015318> (raw)
In-Reply-To: <20260828151024.2081478-1-cosmin-gabriel.tanislav.xa@renesas.com>
On Fri, Aug 28, 2026 at 06:10:24PM +0300, Cosmin Tanislav wrote:
> [You don't often get email from cosmin-gabriel.tanislav.xa@renesas.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Each dmatest worker thread has a pending and a done flag which describe
> the thread's lifecycle.
>
> pending is initialized to true when the thread is added to the threads
> list. pending is set to false once the thread is actually running. done
> is set to true once the thread has finished its testing.
>
> When the wait module parameter is set to true, dmatest_init() waits for
> the !is_threaded_test_run() condition to become true.
>
> If the worker thread is not started and running by the time
> dmatest_init() waits, the !is_threaded_test_run() condition will be true
> and the wait will stop early, before the worker thread is even started.
> dmatest_init() exits, defeating the whole purpose of the wait.
>
> If then we try to remove the module, kthread_stop() will try to cleanup
> the worker threads, interrupting wait_event_freezable_timeout(), which
> will return -ERESTARTSYS, causing the "test timed out" message to be
> printed.
>
> Clear the pending flag once we wake up the worker thread to avoid this
> race.
>
> Fixes: d53513d5dc28 ("dmaengine: dmatest: Add support for multi channel testing")
> Signed-off-by: Cosmin Tanislav <cosmin-gabriel.tanislav.xa@renesas.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
> V2:
> * move pending = false before wake_up_process() as suggested by Sashiko
>
> drivers/dma/dmatest.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/dmatest.c b/drivers/dma/dmatest.c
> index 2ae3469397f3..f654a00e0040 100644
> --- a/drivers/dma/dmatest.c
> +++ b/drivers/dma/dmatest.c
> @@ -610,7 +610,6 @@ static int dmatest_func(void *data)
> ret = -ENOMEM;
>
> smp_rmb();
> - thread->pending = false;
> info = thread->info;
> params = &info->params;
> chan = thread->chan;
> @@ -1141,6 +1140,7 @@ static void run_pending_tests(struct dmatest_info *info)
>
> thread_count = 0;
> list_for_each_entry(thread, &dtc->threads, node) {
> + thread->pending = false;
> wake_up_process(thread->task);
> thread_count++;
> }
> --
> 2.55.0
prev parent reply other threads:[~2026-10-12 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 15:10 Cosmin Tanislav
2026-10-12 10:12 ` claudiu beznea
2026-10-12 14:56 ` 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=asz1CVWrS7zst1rE@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=cosmin-gabriel.tanislav.xa@renesas.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seraj.alijan@sondrel.com \
--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®