linux-kernel - Re: [PATCH] drm/tilcdc: Fix removal actions in case of failed probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251022110424.36a63ad3@kmaincent-XPS-13-7390>
Date: Wed, 22 Oct 2025 11:04:24 +0200
From: Kory Maincent <kory.maincent@...tlin.com>
To: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
Cc: Douglas Anderson <dianders@...omium.org>, Maxime Ripard
 <mripard@...nel.org>, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org, Bajjuri Praneeth <praneeth@...com>, Louis
 Chauvet <louis.chauvet@...tlin.com>, thomas.petazzoni@...tlin.com, Jyri
 Sarha <jyri.sarha@....fi>, Maarten Lankhorst
 <maarten.lankhorst@...ux.intel.com>, Thomas Zimmermann
 <tzimmermann@...e.de>, David Airlie <airlied@...il.com>, Simona Vetter
 <simona@...ll.ch>
Subject: Re: [PATCH] drm/tilcdc: Fix removal actions in case of failed probe

On Wed, 22 Oct 2025 10:58:40 +0200
Kory Maincent <kory.maincent@...tlin.com> wrote:

> On Wed, 22 Oct 2025 10:05:47 +0300
> Tomi Valkeinen <tomi.valkeinen@...asonboard.com> wrote:
> 
> > Hi,
> > 
> > On 14/10/2025 17:32, Kory Maincent wrote:  
> > > From: "Kory Maincent (TI.com)" <kory.maincent@...tlin.com>
> > > 
> > > The drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers
> > > should only be called when the device has been successfully registered.
> > > Currently, these functions are called unconditionally in tilcdc_fini(),
> > > which causes warnings during probe deferral scenarios.
> > > 
> > > [    7.972317] WARNING: CPU: 0 PID: 23 at
> > > drivers/gpu/drm/drm_atomic_state_helper.c:175
> > > drm_atomic_helper_crtc_duplicate_state+0x60/0x68 ... [    8.005820]
> > > drm_atomic_helper_crtc_duplicate_state from
> > > drm_atomic_get_crtc_state+0x68/0x108 [    8.005858]
> > > drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8 [
> > >  8.005885]  drm_atomic_helper_disable_all from
> > > drm_atomic_helper_shutdown+0x90/0x144 [    8.005911]
> > > drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc] [
> > > 8.005957]  tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]
> > > 
> > > Fix this by moving both drm_kms_helper_poll_fini() and
> > > drm_atomic_helper_shutdown() inside the priv->is_registered conditional
> > > block, ensuring they only execute after successful device registration.
> > > 
> > > Fixes: 3c4babae3c4a ("drm: Call drm_atomic_helper_shutdown() at
> > > shutdown/remove time for misc drivers") Signed-off-by: Kory Maincent
> > > (TI.com) <kory.maincent@...tlin.com>    
> > 
> > Should this be cc: stable?  
> 
> Indeed I think so.

Should I send a new version with the stable tag included?

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com