| Message ID | 20230926101909.15030-1-irui.wang@mediatek.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [1/2] media: mediatek: vcodec: Fix encoder access NULL pointer | expand |
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@mediatek.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
Il 26/09/23 12:19, Irui Wang ha scritto: > 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@mediatek.com> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Ping! Is this a fix for 6.6 or not? Regards, Hans On 02/10/2023 12:24, Hans Verkuil wrote: > 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@mediatek.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
On 04/10/2023 08:54, Hans Verkuil wrote: > Ping! Is this a fix for 6.6 or not? > > Regards, > > Hans > > On 02/10/2023 12:24, Hans Verkuil wrote: >> 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@mediatek.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? This looks like a real bug, so I'll queue this up for 6.6. Regards, Hans
Dear Hans, Sorry for late response, we have just returned to office after vacation. Yes, it's a fix and thank you very much for accepting it. Best Regards On Thu, 2023-10-05 at 10:46 +0200, Hans Verkuil wrote: > > External email : Please do not click links or open attachments until > you have verified the sender or the content. > On 04/10/2023 08:54, Hans Verkuil wrote: > > Ping! Is this a fix for 6.6 or not? > > > > Regards, > > > > Hans > > > > On 02/10/2023 12:24, Hans Verkuil wrote: > >> 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@mediatek.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? > > This looks like a real bug, so I'll queue this up for 6.6. > > Regards, > > Hans
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);
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@mediatek.com> --- drivers/media/platform/mediatek/vcodec/encoder/venc_vpu_if.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)