From: Xulin Sun <xulin.sun@windriver.com>
To: nas.chung@chipsnmedia.com, jackson.lee@chipsnmedia.com,
mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
xulin.sun@windriver.com
Subject: [PATCH 2/3] media: wave5: Fix kthread worker destruction in polling mode
Date: Wed, 3 Dec 2025 12:09:34 +0800 [thread overview]
Message-ID: <20251203040935.2685490-3-xulin.sun@windriver.com> (raw)
In-Reply-To: <20251203040935.2685490-1-xulin.sun@windriver.com>
Symptom:
------------[ cut here ]------------
WARNING: CPU: 2 PID: 1034 at kernel/kthread.c:1430 kthread_destroy_worker+0x84/0x98
Modules linked in: wave5(-) rpmsg_ctrl rpmsg_char ...
Call trace:
kthread_destroy_worker+0x84/0x98
wave5_vpu_remove+0xc8/0xe0 [wave5]
platform_remove+0x30/0x58
...
---[ end trace 0000000000000000 ]---
Root cause:
In polling mode (irq < 0), the driver uses hrtimer to periodically
trigger wave5_vpu_timer_callback() which queues work via
kthread_queue_work(). The kthread_destroy_worker() function validates
that both work queues are empty:
* WARN_ON(!list_empty(&worker->work_list))
* WARN_ON(!list_empty(&worker->delayed_work_list))
The original code called kthread_destroy_worker() before hrtimer_cancel(),
creating a race condition where the timer could fire during worker
destruction and queue new work, triggering the WARN_ON.
Fix:
Reorder cleanup sequence:
1) Cancel hrtimer first - stops the timer from firing and prevents
new work from being queued
2) Cancel current work with kthread_cancel_work_sync() - ensures any
in-flight work completes
3) Destroy worker - now both work queues are guaranteed empty, so
kthread_destroy_worker() won't trigger warnings
Signed-off-by: Xulin Sun <xulin.sun@windriver.com>
---
drivers/media/platform/chips-media/wave5/wave5-vpu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/chips-media/wave5/wave5-vpu.c b/drivers/media/platform/chips-media/wave5/wave5-vpu.c
index 23aa3ab51a0e..0bcd48df49d0 100644
--- a/drivers/media/platform/chips-media/wave5/wave5-vpu.c
+++ b/drivers/media/platform/chips-media/wave5/wave5-vpu.c
@@ -352,8 +352,9 @@ static void wave5_vpu_remove(struct platform_device *pdev)
struct vpu_device *dev = dev_get_drvdata(&pdev->dev);
if (dev->irq < 0) {
- kthread_destroy_worker(dev->worker);
hrtimer_cancel(&dev->hrtimer);
+ kthread_cancel_work_sync(&dev->work);
+ kthread_destroy_worker(dev->worker);
}
pm_runtime_dont_use_autosuspend(&pdev->dev);
--
2.49.1
next prev parent reply other threads:[~2025-12-03 4:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 4:09 [PATCH 0/3] media: wave5: Fix critical issues in driver remove path Xulin Sun
2025-12-03 4:09 ` [PATCH 1/3] media: wave5: Fix PM runtime usage count underflow Xulin Sun
2025-12-03 4:09 ` Xulin Sun [this message]
2025-12-03 4:09 ` [PATCH 3/3] media: wave5: Fix device cleanup order to prevent kernel panic Xulin Sun
2025-12-03 18:10 ` [PATCH 0/3] media: wave5: Fix critical issues in driver remove path Nicolas Dufresne
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=20251203040935.2685490-3-xulin.sun@windriver.com \
--to=xulin.sun@windriver.com \
--cc=jackson.lee@chipsnmedia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox