From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Guangshuo Li <lgs201920130244@gmail.com>,
Tiffany Lin <tiffany.lin@mediatek.com>,
Andrew-CT Chen <andrew-ct.chen@mediatek.com>,
Yunfei Dong <yunfei.dong@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Kees Cook <kees@kernel.org>, Tomasz Figa <tfiga@chromium.org>,
Chen-Yu Tsai <wenst@chromium.org>,
Steve Cho <stevecho@chromium.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] media: mediatek: vcodec: fix decoder child device leaks
Date: Tue, 29 Sep 2026 16:26:54 -0400 [thread overview]
Message-ID: <90a604622a614a2de95820bdc73372a3e1d7fb41.camel@collabora.com> (raw)
In-Reply-To: <20260921090808.336112-1-lgs201920130244@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2359 bytes --]
Le lundi 21 septembre 2026 à 17:08 +0800, Guangshuo Li a écrit :
> mtk_vcodec_probe() populates decoder hardware child platform devices on
> platforms that support decoder subdevices. These children must be
> removed with of_platform_depopulate() when they are no longer needed.
>
> If initialization fails after the children have been populated, the
> probe error path releases the parent decoder resources without
> depopulating the child devices. This leaves the child platform devices
> registered.
>
> The remove path has the same issue and leaves the child devices
> registered when the parent decoder driver is unbound.
>
> Depopulate the child devices in the probe error path and in the remove
> path before tearing down the remaining parent resources.
>
> The issue was identified by a static analysis tool I developed and
> confirmed by manual review.
>
> Fixes: c05bada35f01 ("media: mtk-vcodec: Add to support multi hardware decode")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
> .../platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.c b/drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.c
> index e936ed8dffba..592685ad522c 100644
> --- a/drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.c
> +++ b/drivers/media/platform/mediatek/vcodec/decoder/mtk_vcodec_dec_drv.c
> @@ -517,6 +517,8 @@ static int mtk_vcodec_probe(struct platform_device *pdev)
> err_dec_mem_init:
> video_unregister_device(vfd_dec);
> err_reg_cont:
> + if (dev->vdec_pdata->is_subdev_supported)
> + of_platform_depopulate(&pdev->dev);
> if (dev->vdec_pdata->uses_stateless_api)
> media_device_cleanup(&dev->mdev_dec);
> destroy_workqueue(dev->decode_workqueue);
> @@ -569,6 +571,9 @@ static void mtk_vcodec_dec_remove(struct platform_device *pdev)
> {
> struct mtk_vcodec_dec_dev *dev = platform_get_drvdata(pdev);
>
> + if (dev->vdec_pdata->is_subdev_supported)
> + of_platform_depopulate(&pdev->dev);
> +
> destroy_workqueue(dev->decode_workqueue);
This was first for a reason, please keep first.
Nicolas
>
> if (media_devnode_is_registered(dev->mdev_dec.devnode)) {
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-09-29 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 9:08 Guangshuo Li
2026-09-29 20:26 ` Nicolas Dufresne [this message]
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=90a604622a614a2de95820bdc73372a3e1d7fb41.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hverkuil+cisco@kernel.org \
--cc=kees@kernel.org \
--cc=lgs201920130244@gmail.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=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stevecho@chromium.org \
--cc=tfiga@chromium.org \
--cc=tiffany.lin@mediatek.com \
--cc=wenst@chromium.org \
--cc=yunfei.dong@mediatek.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®