mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "CK Hu (胡俊光)" <ck.hu@mediatek.com>
To: "chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
	"hsinyi@chromium.org" <hsinyi@chromium.org>
Cc: "linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"airlied@gmail.com" <airlied@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH] drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip
Date: Tue, 27 Feb 2024 08:14:09 +0000	[thread overview]
Message-ID: <082175a61ae84984120407e415b8858760e43763.camel@mediatek.com> (raw)
In-Reply-To: <20240223212404.3709690-1-hsinyi@chromium.org>

Hi, Hsin-yi:

On Fri, 2024-02-23 at 13:23 -0800, Hsin-Yi Wang wrote:
>  	 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>  It's possible that mtk_crtc->event is NULL in
> mtk_drm_crtc_finish_page_flip().
> 
> pending_needs_vblank value is set by mtk_crtc->event, but in
> mtk_drm_crtc_atomic_flush(), it's is not guarded by the same
> lock in mtk_drm_finish_page_flip(), thus a race condition happens.
> 
> Consider the following case:
> 
> CPU1                              CPU2
> step 1:
> mtk_drm_crtc_atomic_begin()
> mtk_crtc->event is not null,
>                                   step 1:
>                                   mtk_drm_crtc_atomic_flush:
>                                   mtk_drm_crtc_update_config(
>                                       !!mtk_crtc->event)
> step 2:
> mtk_crtc_ddp_irq ->
> mtk_drm_finish_page_flip:
> lock
> mtk_crtc->event set to null,
> pending_needs_vblank set to false
> unlock
>                                   pending_needs_vblank set to true,
> 
>                                   step 2:
>                                   mtk_crtc_ddp_irq ->
>                                   mtk_drm_finish_page_flip called
> again,
>                                   pending_needs_vblank is still true
>                                   //null pointer
> 
> Instead of guarding the entire mtk_drm_crtc_atomic_flush(), it's more
> efficient to just check if mtk_crtc->event is null before use.
> 
> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
> Fixes: 119f5173628a ("drm/mediatek: Add DRM Driver for Mediatek SoC
> MT8173.")

Reviewed-by: CK Hu <ck.hu@mediatek.com>

> ---
>  drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/mediatek/mtk_drm_crtc.c
> b/drivers/gpu/drm/mediatek/mtk_drm_crtc.c
> index db43f9dff912..d645b85f9721 100644
> --- a/drivers/gpu/drm/mediatek/mtk_drm_crtc.c
> +++ b/drivers/gpu/drm/mediatek/mtk_drm_crtc.c
> @@ -95,11 +95,13 @@ static void mtk_drm_crtc_finish_page_flip(struct
> mtk_drm_crtc *mtk_crtc)
>  	struct drm_crtc *crtc = &mtk_crtc->base;
>  	unsigned long flags;
>  
> -	spin_lock_irqsave(&crtc->dev->event_lock, flags);
> -	drm_crtc_send_vblank_event(crtc, mtk_crtc->event);
> -	drm_crtc_vblank_put(crtc);
> -	mtk_crtc->event = NULL;
> -	spin_unlock_irqrestore(&crtc->dev->event_lock, flags);
> +	if (mtk_crtc->event) {
> +		spin_lock_irqsave(&crtc->dev->event_lock, flags);
> +		drm_crtc_send_vblank_event(crtc, mtk_crtc->event);
> +		drm_crtc_vblank_put(crtc);
> +		mtk_crtc->event = NULL;
> +		spin_unlock_irqrestore(&crtc->dev->event_lock, flags);
> +	}
>  }
>  
>  static void mtk_drm_finish_page_flip(struct mtk_drm_crtc *mtk_crtc)
> -- 
> 2.44.0.rc0.258.g7320e95886-goog

      reply	other threads:[~2024-02-27  8:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 21:23 Hsin-Yi Wang
2024-02-27  8:14 ` CK Hu (胡俊光) [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=082175a61ae84984120407e415b8858760e43763.camel@mediatek.com \
    --to=ck.hu@mediatek.com \
    --cc=airlied@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hsinyi@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=p.zabel@pengutronix.de \
    /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®