[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <165536598378.1275350.14174129398362283973.b4-ty@cerno.tech>
Date: Thu, 16 Jun 2022 09:53:06 +0200
From: Maxime Ripard <maxime@...no.tech>
To: Chen-Yu Tsai <wens@...e.org>, Samuel Holland <samuel@...lland.org>,
Maxime Ripard <mripard@...nel.org>,
Jernej Skrabec <jernej.skrabec@...il.com>
Cc: Maxime Ripard <maxime@...no.tech>, linux-sunxi@...ts.linux.dev,
Ondrej Jirman <megous@...ous.com>,
dri-devel@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org,
David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
Daniel Vetter <daniel@...ll.ch>
Subject: Re: [PATCH] drm/sun4i: Fix crash during suspend after component bind failure
On Wed, 15 Jun 2022 00:42:53 -0500, Samuel Holland wrote:
> If the component driver fails to bind, or is unbound, the driver data
> for the top-level platform device points to a freed drm_device. If the
> system is then suspended, the driver passes this dangling pointer to
> drm_mode_config_helper_suspend(), which crashes.
>
> Fix this by only setting the driver data while the platform driver holds
> a reference to the drm_device.
>
> [...]
Applied to drm/drm-misc (drm-misc-fixes).
Thanks!
Maxime
Powered by blists - more mailing lists