From: Yunfei Dong <yunfei.dong@mediatek.com>
To: "Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Benjamin Gaignard" <benjamin.gaignard@collabora.com>,
"Nathan Hebert" <nhebert@chromium.org>,
"Irui Wang" <irui.wang@mediatek.com>
Cc: Hsin-Yi Wang <hsinyi@chromium.org>,
Fritz Koenig <frkoenig@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>,
Steve Cho <stevecho@chromium.org>,
Yunfei Dong <yunfei.dong@mediatek.com>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: [PATCH v3,0/2] media: adding lock to protect the context list
Date: Thu, 22 Feb 2024 17:26:07 +0800 [thread overview]
Message-ID: <20240222092609.31382-1-yunfei.dong@mediatek.com> (raw)
From: Yunfei Dong <yunfei.dong@mediatek.corp-partner.google.com>
The ctx_list of each module will be deleted when scp getting unexpected
behavior, then the ctx_list->next will be set to NULL, the system reboot
when access the NULL pointer in function vpu_enc(dev)_ipi_handler to go
through each context.
---
Changed in v3:
- change 'Fixes' tag in patch 1/2
- add cover-letter for this patch series
---
Yunfei Dong (2):
media: mediatek: vcodec: adding lock to protect decoder context list
media: mediatek: vcodec: adding lock to protect encoder context list
.../platform/mediatek/vcodec/common/mtk_vcodec_fw_vpu.c | 8 ++++----
.../platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.c | 5 +++++
.../platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.h | 2 ++
.../media/platform/mediatek/vcodec/decoder/vdec_vpu_if.c | 2 ++
.../platform/mediatek/vcodec/encoder/mtk_vcodec_enc_drv.c | 5 +++++
.../platform/mediatek/vcodec/encoder/mtk_vcodec_enc_drv.h | 2 ++
.../media/platform/mediatek/vcodec/encoder/venc_vpu_if.c | 2 ++
7 files changed, 22 insertions(+), 4 deletions(-)
--
2.18.0
next reply other threads:[~2024-02-22 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 9:26 Yunfei Dong [this message]
2024-02-22 9:26 ` [PATCH v3,1/2] media: mediatek: vcodec: adding lock to protect decoder context list Yunfei Dong
2024-02-23 8:28 ` AngeloGioacchino Del Regno
2024-02-23 18:11 ` Nicolas Dufresne
2024-02-26 19:39 ` Nicolas Dufresne
2024-02-26 21:32 ` Nicolas Dufresne
2024-03-13 13:46 ` Sebastian Fricke
2024-02-22 9:26 ` [PATCH v3,2/2] media: mediatek: vcodec: adding lock to protect encoder " Yunfei Dong
2024-02-23 8:28 ` AngeloGioacchino Del Regno
2024-02-23 18:11 ` Nicolas Dufresne
2024-03-13 13:44 ` Sebastian Fricke
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=20240222092609.31382-1-yunfei.dong@mediatek.com \
--to=yunfei.dong@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=frkoenig@chromium.org \
--cc=hsinyi@chromium.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=irui.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nfraprado@collabora.com \
--cc=nhebert@chromium.org \
--cc=nicolas.dufresne@collabora.com \
--cc=stevecho@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).