[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20210722093821.nnmcldjts2boxctu@gilmour>
Date: Thu, 22 Jul 2021 11:38:21 +0200
From: Maxime Ripard <maxime@...no.tech>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Robert Foss <robert.foss@...aro.org>,
Andrzej Hajda <a.hajda@...sung.com>,
Daniel Vetter <daniel.vetter@...el.com>,
David Airlie <airlied@...ux.ie>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Neil Armstrong <narmstrong@...libre.com>,
Jonas Karlman <jonas@...boo.se>,
Jernej Skrabec <jernej.skrabec@...il.com>,
Thierry Reding <thierry.reding@...il.com>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 08/10] drm/panel: raspberrypi-touchscreen: Prevent
double-free
On Tue, Jul 20, 2021 at 07:19:40PM +0200, Sam Ravnborg wrote:
> Hi Maxime,
> On Tue, Jul 20, 2021 at 03:45:23PM +0200, Maxime Ripard wrote:
> > The mipi_dsi_device allocated by mipi_dsi_device_register_full() is
> > already free'd on release.
> >
> > Fixes: 2f733d6194bd ("drm/panel: Add support for the Raspberry Pi 7" Touchscreen.")
> > Signed-off-by: Maxime Ripard <maxime@...no.tech>
>
> Reviewed-by: Sam Ravnborg <sam@...nborg.org>
Thanks, I applied it to drm-misc-fixes
> I did a quick audit (as using grep mostly) to see if other panels had
> the same bug, but did not find others.
Yeah, the RaspberryPi panel seems to be the only odd DSI panel not
controlled through DCS, and the other panels don't have to allocate the
mipi-dsi device anyway.
No bridge seems to have the issue though.
Maxime
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists