mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ming Qian(OSS)" <ming.qian@oss.nxp.com>
To: Myeonghun Pak <mhun512@gmail.com>, Ming Qian <ming.qian@nxp.com>,
	Zhou Peng <eagle.zhou@nxp.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Ijae Kim <ae878000@gmail.com>
Subject: Re: [PATCH v4 1/2] media: amphion: drain message work before releasing core state
Date: Tue, 29 Sep 2026 09:42:47 +0800	[thread overview]
Message-ID: <2bb40419-6e9a-4a7c-aea2-7e811037ed16@oss.nxp.com> (raw)
In-Reply-To: <20260925191706.3144437-2-mhun512@gmail.com>



On 9/26/2026 3:17 AM, Myeonghun Pak wrote:
> vpu_core_unregister() frees core->msg_buffer before cancelling the message
> workers, although core->msg_fifo still uses the buffer as its backing
> storage. A queued worker can read it after it has been freed.
> 
> Drain the core and instance message work first, then release core->vpu
> and the FIFO buffer. This follows the ordering in vpu_core_suspend().
> 
> Fixes: 9f599f351e86 ("media: amphion: add vpu core driver")
> Cc: stable@vger.kernel.org
> Co-developed-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>

Reviewed-by: Ming Qian <ming.qian@oss.nxp.com>

> ---
>   drivers/media/platform/amphion/vpu_core.c | 15 ++++++++-------
>   1 file changed, 8 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/media/platform/amphion/vpu_core.c b/drivers/media/platform/amphion/vpu_core.c
> index 85cc4a14f8ed..a0c58ec97a42 100644
> --- a/drivers/media/platform/amphion/vpu_core.c
> +++ b/drivers/media/platform/amphion/vpu_core.c
> @@ -299,22 +299,23 @@ static void vpu_core_put_vpu(struct vpu_core *core)
>   	core->vpu->put_vpu(core->vpu);
>   }
>   
> +static void vpu_core_cancel_work(struct vpu_core *core);
> +
>   static int vpu_core_unregister(struct device *dev, struct vpu_core *core)
>   {
>   	list_del_init(&core->list);
>   
> -	vpu_core_put_vpu(core);
> -	core->vpu = NULL;
> -	kfree(core->msg_buffer);
> -	core->msg_buffer = NULL;
> -
>   	if (core->workqueue) {
> -		cancel_work_sync(&core->msg_work);
> -		cancel_delayed_work_sync(&core->msg_delayed_work);
> +		vpu_core_cancel_work(core);
>   		destroy_workqueue(core->workqueue);
>   		core->workqueue = NULL;
>   	}
>   
> +	vpu_core_put_vpu(core);
> +	core->vpu = NULL;
> +	kfree(core->msg_buffer);
> +	core->msg_buffer = NULL;
> +
>   	return 0;
>   }
>   


  reply	other threads:[~2026-09-29  1:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 19:17 [PATCH v4 0/2] media: amphion: fix VPU core lifetime during teardown Myeonghun Pak
2026-09-25 19:17 ` [PATCH v4 1/2] media: amphion: drain message work before releasing core state Myeonghun Pak
2026-09-29  1:42   ` Ming Qian(OSS) [this message]
2026-09-25 19:17 ` [PATCH v4 2/2] media: amphion: prevent unbind while video instances are open Myeonghun Pak
2026-09-29  1:43   ` Ming Qian(OSS)

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=2bb40419-6e9a-4a7c-aea2-7e811037ed16@oss.nxp.com \
    --to=ming.qian@oss.nxp.com \
    --cc=ae878000@gmail.com \
    --cc=eagle.zhou@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mhun512@gmail.com \
    --cc=ming.qian@nxp.com \
    --cc=stable@vger.kernel.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

all inboxes | Powered by JetHome®