mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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,
	nicolas.dufresne@collabora.com, hverkuil@kernel.org,
	dafna.hirschfeld@collabora.com, xulin.sun@windriver.com
Subject: [PATCH v2 0/3] media: wave5: Fix critical issues in driver remove path
Date: Thu,  4 Dec 2025 17:41:50 +0800	[thread overview]
Message-ID: <20251204094153.1530331-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 during extensive testing with
gstreamer encoding pipelines and module load/unload cycles.

v1: https://lore.kernel.org/linux-media/20251203040935.2685490-1-xulin.sun@windriver.com

Changes in v2:
- Reformatted commit messages per maintainer feedback
  * Removed "Symptom:/Root cause:/Fix:" section titles
  * Reordered content: fix description → root cause → symptoms
  * Added Fixes: tags for backport tracking
- Retested on media/master (6.18-rc5)
  * All three issues still exist in the code logic
  * Issues are harder to trigger on 6.18-rc5
  * Applied patches resolve all issues on both 6.12.58-rt6 and 6.18-rc5

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

Testing performed:
- 50+ consecutive H.264/H.265 encoding operations
- 100+ modprobe/rmmod cycles
- Tested on both 6.12.58-rt6 (TI AM62A) and 6.18-rc5
- No warnings or crashes observed after applying patches

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

             reply	other threads:[~2025-12-04  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  9:41 Xulin Sun [this message]
2025-12-04  9:41 ` [PATCH v2 1/3] media: wave5: Fix PM runtime usage count underflow Xulin Sun
2025-12-04  9:41 ` [PATCH v2 2/3] media: wave5: Fix kthread worker destruction in polling mode Xulin Sun
2025-12-04  9:41 ` [PATCH v2 3/3] media: wave5: Fix device cleanup order to prevent kernel panic Xulin Sun

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=20251204094153.1530331-1-xulin.sun@windriver.com \
    --to=xulin.sun@windriver.com \
    --cc=dafna.hirschfeld@collabora.com \
    --cc=hverkuil@kernel.org \
    --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 \
    --cc=nicolas.dufresne@collabora.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

all inboxes | Powered by JetHome®