All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Runyu Xiao <runyu.xiao@seu.edu.cn>
Cc: Rob Clark <robin.clark@oss.qualcomm.com>,
	Dave Airlie <airlied@gmail.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Jianhao Xu <jianhao.xu@seu.edu.cn>
Subject: Re: [PATCH] fbdev: omapfb: panel-dsi-cm: initialize lock before registering display
Date: Tue, 18 Aug 2026 18:49:50 +0200	[thread overview]
Message-ID: <27cdcd5f-7cbc-4e22-8ac3-81d427c68f1d@gmx.de> (raw)
In-Reply-To: <20260818135318.1957283-1-runyu.xiao@seu.edu.cn>

On 8/18/26 15:53, Runyu Xiao wrote:
> dsicm_probe() registers the display before initializing ddata->lock.
> Once omapdss_register_display() publishes the display, another consumer
> can reach a dsicm callback that takes this mutex while it is still
> uninitialized.
> 
> Initialize the mutex before registering the display so the published
> callbacks always see a valid lock.
> 
> Fixes: f76ee892a99e ("omapfb: copy omapdss & displays for omapfb")
> Cc: stable@vger.kernel.org
> Signed-off-by: Runyu Xiao <runyu.xiao@seu.edu.cn>
> ---
>   drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
applied.

Thanks!
Helge

      parent reply	other threads:[~2026-08-18 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 13:53 [PATCH] fbdev: omapfb: panel-dsi-cm: initialize lock before registering display Runyu Xiao
2026-08-18 14:07 ` sashiko-bot
2026-08-18 16:49 ` Helge Deller [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=27cdcd5f-7cbc-4e22-8ac3-81d427c68f1d@gmx.de \
    --to=deller@gmx.de \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jianhao.xu@seu.edu.cn \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=runyu.xiao@seu.edu.cn \
    --cc=stable@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.