mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: Nathan Chancellor <nathan@kernel.org>,
	Jocelyn Falempe <jfalempe@redhat.com>,
	Javier Martinez Canillas <javierm@redhat.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] drm/panic: Avoid crash from invalid CONFIG_DRM_PANIC_SCREEN values
Date: Fri, 9 Jan 2026 08:55:37 +0000	[thread overview]
Message-ID: <b2197fa6-ab12-41ee-88fd-c57f6caa681e@igalia.com> (raw)
In-Reply-To: <20260105-drm_panic-handle-invalid-drm_panic_screen-v1-0-55228bd4b0f8@kernel.org>


On 06/01/2026 06:19, Nathan Chancellor wrote:
> 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.

I've pushed the series to drm-misc-next, thanks for fixing it up!

Regards,

Tvrtko

> 
> ---
> 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@kernel.org>
> 


      parent reply	other threads:[~2026-01-09  8:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  6:19 Nathan Chancellor
2026-01-06  6:19 ` [PATCH 1/2] drm/panic: Ensure drm_panic_type is initialized to a valid value Nathan Chancellor
2026-01-06  8:24   ` Tvrtko Ursulin
2026-01-06 21:32   ` Jocelyn Falempe
2026-01-06  6:19 ` [PATCH 2/2] drm/panic: Fix expected string for QR_CODE in drm_panic_type_map Nathan Chancellor
2026-01-06  8:19   ` Tvrtko Ursulin
2026-01-06 21:34   ` Jocelyn Falempe
2026-01-09  8:55 ` Tvrtko Ursulin [this message]

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=b2197fa6-ab12-41ee-88fd-c57f6caa681e@igalia.com \
    --to=tvrtko.ursulin@igalia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=jfalempe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nathan@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®