From: Jocelyn Falempe <jfalempe@redhat.com>
To: Devin Wittmayer <lucid_duck@justthetip.ca>,
Javier Martinez Canillas <javierm@redhat.com>
Cc: 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>,
Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/panic: Accept a trailing newline in panic_screen
Date: Fri, 16 Oct 2026 23:18:44 +0200 [thread overview]
Message-ID: <f651c7f8-9651-4d9b-bde8-3c0de767a66f@redhat.com> (raw)
In-Reply-To: <20261016052722.60051-2-lucid_duck@justthetip.ca>
On 10/16/26 07:27, Devin Wittmayer wrote:
> Setting the panic screen through sysfs with echo fails with EINVAL,
> because the value ends in a newline. Ignore it when matching.
Thanks it looks good to me.
Reviewed-by: Jocelyn Falempe <jfalempe@redhat.com>
>
> Fixes: e85e9ccf3f84 ("drm/panic: Report invalid or unsupported panic modes")
> Signed-off-by: Devin Wittmayer <lucid_duck@justthetip.ca>
> ---
> QEMU, 10 runs each, on drm-misc-fixes and drm-misc-next:
>
> before after
> write of "user\n" refused takes
> write of "bsod\n" refused refused
> drm.panic_screen=user at boot takes takes
>
> amdgpu, 2 runs each, 7.2.6 with Arch's source and config:
>
> echo user refused takes
>
> drivers/gpu/drm/drm_panic.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_panic.c b/drivers/gpu/drm/drm_panic.c
> index 29b1487de7ae0..7847b38ba9aab 100644
> --- a/drivers/gpu/drm/drm_panic.c
> +++ b/drivers/gpu/drm/drm_panic.c
> @@ -839,7 +839,7 @@ static int drm_panic_type_set(const char *val, const struct kernel_param *kp)
> unsigned int i;
>
> for (i = 0; i < ARRAY_SIZE(drm_panic_type_map); i++) {
> - if (!strcmp(val, drm_panic_type_map[i])) {
> + if (sysfs_streq(val, drm_panic_type_map[i])) {
> drm_panic_type = i;
> return 0;
> }
next prev parent reply other threads:[~2026-10-16 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 5:27 [PATCH 1/2] drm/panic: Fix kmsg screen hang on a long log line Devin Wittmayer
2026-10-16 5:27 ` [PATCH 2/2] drm/panic: Accept a trailing newline in panic_screen Devin Wittmayer
2026-10-16 7:47 ` Tvrtko Ursulin
2026-10-16 21:18 ` Jocelyn Falempe [this message]
[not found] ` <sashiko-outbox-173828@kernel.org>
2026-10-16 15:29 ` [PATCH 1/2] drm/panic: Fix kmsg screen hang on a long log line Devin Wittmayer
2026-10-16 21:09 ` Jocelyn Falempe
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=f651c7f8-9651-4d9b-bde8-3c0de767a66f@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tvrtko.ursulin@igalia.com \
--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®