From: Vinod Koul <vkoul@kernel.org>
To: Jie Hai <haijie1@huawei.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: dmatest: fix timeout caused by kthread_stop
Date: Wed, 17 Apr 2024 22:48:36 +0530 [thread overview]
Message-ID: <ZiAEbOMxy9pBcOX5@matsya> (raw)
In-Reply-To: <20230720114102.51053-1-haijie1@huawei.com>
On 20-07-23, 19:41, Jie Hai wrote:
> The change introduced by commit a7c01fa93aeb ("signal: break
> out of wait loops on kthread_stop()") causes dmatest aborts
> any ongoing tests and possible failure on the tests. This patch
Have you see this failure? Any log of that..
> use wait_event_timeout instead of wait_event_freezable_timeout
> to avoid interrupting ongoing tests by signal brought by
> kthread_stop().
>
> Signed-off-by: Jie Hai <haijie1@huawei.com>
> ---
> 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 ffe621695e47..c06b8b16645a 100644
> --- a/drivers/dma/dmatest.c
> +++ b/drivers/dma/dmatest.c
> @@ -827,7 +827,7 @@ static int dmatest_func(void *data)
> } else {
> dma_async_issue_pending(chan);
>
> - wait_event_freezable_timeout(thread->done_wait,
> + ret = wait_event_timeout(thread->done_wait,
> done->done,
> msecs_to_jiffies(params->timeout));
>
> --
> 2.33.0
--
~Vinod
next prev parent reply other threads:[~2024-04-17 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 11:41 [PATCH] dmaengine: dmatest: fix timeout caused by kthread_stop Jie Hai
2023-09-25 1:10 ` Jie Hai
2023-12-08 1:53 ` Jie Hai
2024-01-31 1:32 ` Jie Hai
2024-04-17 17:18 ` Vinod Koul [this message]
2024-04-23 3:39 ` Jie Hai
2024-04-25 9:05 ` Vinod Koul
2024-04-25 12:40 ` [PATCH v2] " Jie Hai
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=ZiAEbOMxy9pBcOX5@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=haijie1@huawei.com \
--cc=linux-kernel@vger.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 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.