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 0/3] media: wave5: Fix critical issues in driver remove path
Date: Wed, 3 Dec 2025 12:09:32 +0800 [thread overview]
Message-ID: <20251203040935.2685490-1-xulin.sun@windriver.com> (raw)
This patch series fixes three critical issues in the wave5 VPU driver's
remove path that cause kernel warnings and system crashes.
The issues were discovered and consistently reproduced on kernel 6.12.58-rt6
with the TI AM62A platform. While testing on kernel 6.18 shows the issues
are harder to trigger, the underlying logic problems still exist in the code.
Patch 1: Fixes PM runtime reference count underflow
Patch 2: Fixes kthread worker destruction warning
Patch 3: Fixes kernel panic due to incorrect cleanup order
All patches have been tested with 50+ consecutive encoding operations and
multiple modprobe/rmmod cycles without any warnings or crashes on 6.12.58-rt6.
Xulin Sun (3):
media: wave5: Fix PM runtime usage count underflow
media: wave5: Fix kthread worker destruction in polling mode
media: wave5: Fix device cleanup order to prevent kernel panic
drivers/media/platform/chips-media/wave5/wave5-vpu.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
--
2.49.1
next 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 Xulin Sun [this message]
2025-12-03 4:09 ` [PATCH 1/3] media: wave5: Fix PM runtime usage count underflow Xulin Sun
2025-12-03 4:09 ` [PATCH 2/3] media: wave5: Fix kthread worker destruction in polling mode Xulin Sun
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-1-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