[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20260105-drm_panic-handle-invalid-drm_panic_screen-v1-0-55228bd4b0f8@kernel.org>
Date: Mon, 05 Jan 2026 23:19:25 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Jocelyn Falempe <jfalempe@...hat.com>,
Javier Martinez Canillas <javierm@...hat.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
Tvrtko Ursulin <tvrtko.ursulin@...lia.com>
Cc: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Nathan Chancellor <nathan@...nel.org>
Subject: [PATCH 0/2] drm/panic: Avoid crash from invalid
CONFIG_DRM_PANIC_SCREEN values
Hi all,
This series addresses a couple of issues I noticed when accessing
/sys/module/drm/parameters/panic_screen on my Arch Linux machines, which
have "qr_code" as the value of CONFIG_DRM_PANIC_SCREEN. This happened to
be unsupported in my configuration since I was missing some Rust
dependencies in my environment for CONFIG_DRM_PANIC_SCREEN_QR_CODE,
resulting in a kernel crash. Patch one addresses the root cause of the
crash and patch two addresses an inconsistency I noticed between this
new code and the documented value for CONFIG_DRM_PANIC_SCREEN in Kconfig
for qr_code.
If there are any issues, please let me know.
---
Nathan Chancellor (2):
drm/panic: Ensure drm_panic_type is initialized to a valid value
drm/panic: Fix expected string for QR_CODE in drm_panic_type_map
drivers/gpu/drm/drm_panic.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
---
base-commit: 349d4efadc1f831ebc0b872ba1e3a2b7dd58b72b
change-id: 20260105-drm_panic-handle-invalid-drm_panic_screen-097e49e21c49
Best regards,
--
Nathan Chancellor <nathan@...nel.org>
Powered by blists - more mailing lists