From: Ruben Wauters <rubenru09@aol.com>
To: Shenghao Yang <me@shenghaoyang.info>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/gud: fix NULL fb and crtc dereferences on USB disconnect
Date: Sat, 03 Jan 2026 17:23:33 +0000 [thread overview]
Message-ID: <28c39f1979452b24ddde4de97e60ca721334eb49.camel@aol.com> (raw)
In-Reply-To: <20251231055039.44266-1-me@shenghaoyang.info>
[-- Attachment #1: Type: text/plain, Size: 3079 bytes --]
Hi
On Wed, 2025-12-31 at 13:50 +0800, Shenghao Yang wrote:
> On disconnect drm_atomic_helper_disable_all() is called which
> sets both the fb and crtc for a plane to NULL before invoking a commit.
>
> This causes a kernel oops on every display disconnect.
>
> Add guards for those dereferences.
>
> Cc: <stable@vger.kernel.org> # 6.18.x
> Signed-off-by: Shenghao Yang <me@shenghaoyang.info>
> ---
> drivers/gpu/drm/gud/gud_pipe.c | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/gpu/drm/gud/gud_pipe.c b/drivers/gpu/drm/gud/gud_pipe.c
> index 76d77a736d84..4b77be94348d 100644
> --- a/drivers/gpu/drm/gud/gud_pipe.c
> +++ b/drivers/gpu/drm/gud/gud_pipe.c
> @@ -457,27 +457,20 @@ int gud_plane_atomic_check(struct drm_plane *plane,
> struct drm_plane_state *old_plane_state = drm_atomic_get_old_plane_state(state, plane);
> struct drm_plane_state *new_plane_state = drm_atomic_get_new_plane_state(state, plane);
> struct drm_crtc *crtc = new_plane_state->crtc;
> - struct drm_crtc_state *crtc_state;
> + struct drm_crtc_state *crtc_state = NULL;
> const struct drm_display_mode *mode;
> struct drm_framebuffer *old_fb = old_plane_state->fb;
> struct drm_connector_state *connector_state = NULL;
> struct drm_framebuffer *fb = new_plane_state->fb;
> - const struct drm_format_info *format = fb->format;
> + const struct drm_format_info *format;
> struct drm_connector *connector;
> unsigned int i, num_properties;
> struct gud_state_req *req;
> int idx, ret;
> size_t len;
>
> - if (drm_WARN_ON_ONCE(plane->dev, !fb))
> - return -EINVAL;
> -
> - if (drm_WARN_ON_ONCE(plane->dev, !crtc))
> - return -EINVAL;
With the elimination of these two WARN_ON_ONCEs, it's possible that
crtc_state may not be assigned below, and therefore may be read/passed
to functions when it is NULL (e.g. line 488). Either protection for a
null crtc_state should be added to the rest of the function, or the
function shouldn't continue if crtc is NULL.
Ruben
> - crtc_state = drm_atomic_get_new_crtc_state(state, crtc);
> -
> - mode = &crtc_state->mode;
> + if (crtc)
> + crtc_state = drm_atomic_get_new_crtc_state(state, crtc);
>
> ret = drm_atomic_helper_check_plane_state(new_plane_state, crtc_state,
> DRM_PLANE_NO_SCALING,
> @@ -492,6 +485,9 @@ int gud_plane_atomic_check(struct drm_plane *plane,
> if (old_plane_state->rotation != new_plane_state->rotation)
> crtc_state->mode_changed = true;
>
> + mode = &crtc_state->mode;
> + format = fb->format;
> +
> if (old_fb && old_fb->format != format)
> crtc_state->mode_changed = true;
>
> @@ -598,7 +594,7 @@ void gud_plane_atomic_update(struct drm_plane *plane,
> struct drm_atomic_helper_damage_iter iter;
> int ret, idx;
>
> - if (crtc->state->mode_changed || !crtc->state->enable) {
> + if (!crtc || crtc->state->mode_changed || !crtc->state->enable) {
> cancel_work_sync(&gdrm->work);
> mutex_lock(&gdrm->damage_lock);
> if (gdrm->fb) {
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-03 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 5:50 Shenghao Yang
2026-01-03 17:23 ` Ruben Wauters [this message]
2026-01-03 17:47 ` Shenghao Yang
2026-01-03 19:18 ` Ruben Wauters
2026-01-04 16:30 ` Shenghao Yang
2026-01-07 7:46 ` Thomas Zimmermann
2026-01-07 15:02 ` Ruben Wauters
2026-01-07 15:56 ` Thomas Zimmermann
2026-01-08 13:39 ` Shenghao Yang
2026-01-13 14:05 ` Ruben Wauters
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=28c39f1979452b24ddde4de97e60ca721334eb49.camel@aol.com \
--to=rubenru09@aol.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=me@shenghaoyang.info \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®