Thread (2 messages) flat view 2 messages, 2 authors, 15d ago

Re: [PATCH] fbdev: omapfb: panel-dsi-cm: initialize lock before registering display

From: Helge Deller <deller@gmx.de>
Date: 2026-08-18 16:49:58
Also in: dri-devel, linux-omap, lkml, stable

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 <redacted>
---
  drivers/video/fbdev/omap2/omapfb/displays/panel-dsi-cm.c | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)
applied.

Thanks!
Helge
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help