Re: linux-next: manual merge of the drm tree with the drm-misc-fixes tree
From: desobei
Date: Thu Nov 19 2026 - 01:14:01 EST
On Mon, Oct 19, 2026 at 12:09:59PM -0700, Devin Wittmayer wrote:
> Two of those fixes are mine, so I had a go at it. The code that draws
> the panic screen was moved into drm_panic_helper.c in drm-next, so two of
> the three need to move with it.
[...]
> The drm_panic KUnit tests pass with and without it.
Without it they can hang, depending on what is in the kernel log.
Both fixes are still missing from drm_panic_helper.c in next-20261118
and in today's drm-misc-next and drm-next: kmsg_buf is still 512 bytes
and the empty read check is not there.
On next-20261117, the drm_panic_helper KUnit suite never finishes once
it reaches the kmsg screen cases if the log holds a record longer than
512 bytes. Booting under virtme-ng is enough to trigger it, since its
kernel command line is around 650 characters. The user screen cases
pass, then the suite stalls and the boot never reaches init. One run
sat there for 50 minutes before I killed it.
With your resolution applied on top of next-20261117, all 30 cases
(user and kmsg screens, all three tests) pass and the boot completes.
Tested in x86_64 QEMU/KVM guests with 8 vCPUs and KASAN and lockdep
enabled, with the suite built in and selected with
kunit.filter_glob=drm_panic_helper.
Tested-by: desobei <desobei@xxxxxxxxxxx>
Is anyone planning to send this as a patch for drm-misc-next, or to fold
it into the next drm merge? I'm happy to turn it into a patch if that
helps.
I found this with the help of an AI coding assistant (Claude Opus 5.5).