[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36356e37-9abd-4dec-a716-9822b67bd0fa@xs4all.nl>
Date: Mon, 2 Oct 2023 12:24:01 +0200
From: Hans Verkuil <hverkuil-cisco@...all.nl>
To: Irui Wang <irui.wang@...iatek.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
angelogioacchino.delregno@...labora.com,
nicolas.dufresne@...labora.com,
Yunfei Dong <yunfei.dong@...iatek.com>
Cc: Project_Global_Chrome_Upstream_Group@...iatek.com,
linux-media@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Maoguang Meng <maoguang.meng@...iatek.com>
Subject: Re: [PATCH 1/2] media: mediatek: vcodec: Fix encoder access NULL
pointer
On 26/09/2023 12:19, Irui Wang wrote:
> Need to set the private data with encoder device, or will access
> NULL pointer in encoder handler.
>
> Fixes: 1972e32431ed ("media: mediatek: vcodec: Fix possible invalid memory access for encoder")
>
> Signed-off-by: Irui Wang <irui.wang@...iatek.com>
> ---
> drivers/media/platform/mediatek/vcodec/encoder/venc_vpu_if.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/mediatek/vcodec/encoder/venc_vpu_if.c b/drivers/media/platform/mediatek/vcodec/encoder/venc_vpu_if.c
> index d299cc2962a5..ae6290d28f8e 100644
> --- a/drivers/media/platform/mediatek/vcodec/encoder/venc_vpu_if.c
> +++ b/drivers/media/platform/mediatek/vcodec/encoder/venc_vpu_if.c
> @@ -138,7 +138,8 @@ int vpu_enc_init(struct venc_vpu_inst *vpu)
> vpu->ctx->vpu_inst = vpu;
>
> status = mtk_vcodec_fw_ipi_register(vpu->ctx->dev->fw_handler, vpu->id,
> - vpu_enc_ipi_handler, "venc", NULL);
> + vpu_enc_ipi_handler, "venc",
> + vpu->ctx->dev);
>
> if (status) {
> mtk_venc_err(vpu->ctx, "vpu_ipi_register fail %d", status);
Is this a fix that should go to 6.6?
Regards,
Hans
Powered by blists - more mailing lists