Subject: linux-next: build failure after merge of the kthread tree

From: Thierry Reding <[email-masked]>
Date: Tue, 28 Apr 2026 14:56:53 +0200

Hi all,

After merging the amdgpu tree, today's linux-next build (arm64 allyesconfig)
failed like this:

    /srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn21/display_mode_vba_21.c: In function 'dml21_ModeSupportAndSystemConfigurationFull':
    /srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn21/display_mode_vba_21.c:5244:1: error: the frame size of 3232 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]
     5244 | }
          | ^
    cc1: all warnings being treated as errors
    make[7]: *** [/srv/kbuild/next/linux.git/scripts/Makefile.build:289: drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn21/display_mode_vba_21.o] Error 1
    make[7]: *** Waiting for unfinished jobs....
    /srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.c: In function 'dml30_ModeSupportAndSystemConfigurationFull':
    /srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.c:4961:1: error: the frame size of 3360 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]
     4961 | }
          | ^
    cc1: all warnings being treated as errors
    make[7]: *** [/srv/kbuild/next/linux.git/scripts/Makefile.build:289: drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn30/display_mode_vba_30.o] Error 1
    /srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_32.c: In function 'dml32_ModeSupportAndSystemConfigurationFull':
    /srv/kbuild/next/linux.git/drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn32/display_mode_vba_32.c:3762:1: error: the frame size of 3968 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]
     3762 | } // ModeSupportAndSystemConfigurationFull
          | ^
    cc1: all warnings being treated as errors

It's not clear to me what commit caused this, and looking at the mailing
lists it seems like this may have existed for a while and for different
configurations. I don't know if there any plans to try and fix this.

Thierry