From: Myeonghun Pak <mhun512@gmail.com>
To: Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>
Cc: Bryan O'Donoghue <bod@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>,
stable@vger.kernel.org, Ijae Kim <ae878000@gmail.com>
Subject: [PATCH v5 0/2] media: venus: fix HFI teardown races
Date: Fri, 23 Oct 2026 22:40:49 -0400 [thread overview]
Message-ID: <20261023223635.3c895c4752c4-1-mhun512@gmail.com> (raw)
This issue was identified as part of our ongoing research while
reviewing kernel code.
Synchronize IRQ handlers before freeing HFI state, and disable recovery
work at the start of remove to prevent it from racing with teardown.
Changes in v5:
- Patch 1: no code changes; carry Bryan's Reviewed-by.
- Patch 2: drop the duplicate work disable from venus_hfi_destroy(),
keeping it only in venus_remove(), as requested by Bryan.
- Rebase onto media-committers.git next.
Compilation test completed.
v4: https://lore.kernel.org/all/20261001175502.4045853-1-mhun512@gmail.com/
Myeonghun Pak (2):
media: venus: hfi: disable IRQ before freeing HFI device
media: venus: disable recovery work before HFI teardown
drivers/media/platform/qcom/venus/core.c | 2 +-
drivers/media/platform/qcom/venus/hfi_venus.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
base-commit: d7e7bca7169873b46e857c025c10f3336c1258d8
--
2.53.0
next reply other threads:[~2026-10-24 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 2:40 Myeonghun Pak [this message]
2026-10-24 2:40 ` [PATCH v5 1/2] media: venus: hfi: disable IRQ before freeing HFI device Myeonghun Pak
2026-10-24 2:40 ` [PATCH v5 2/2] media: venus: disable recovery work before HFI teardown Myeonghun Pak
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=20261023223635.3c895c4752c4-1-mhun512@gmail.com \
--to=mhun512@gmail.com \
--cc=ae878000@gmail.com \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vikash.garodia@oss.qualcomm.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®