Re: linux-next: build failure after merge of the drm-misc tree
From: Alex Deucher
Date: Wed Sep 23 2026 - 10:15:35 EST
On Wed, Sep 23, 2026 at 9:25 AM Mark Brown <broonie@xxxxxxxxxx> wrote:
>
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> /tmp/next/build/drivers/gpu/drm/amd/amdgpu/../display/dc/dc_memory_pool.c:87:37: error: stack frame size (8264) exceeds limit (2048) in 'dc_memory_pool_create' [-Werror,-Wframe-larger-than]
> 87 | __must_check struct dc_memory_pool *dc_memory_pool_create(size_t size,
> |
>
> which I am exceptionally frustrated to see was caused by commit
>
> bc3f07516a992 (Merge drm/drm-next into drm-misc-next)
>
> which merged the bug I originally reported in the amdgpu tree:
>
> https://lore.kernel.org/r/aq0vYhZXtMqA41wZ@xxxxxxxxxxxxx
>
> and then in the drm tree when that was sent upstream without the report
> having been addressed in any way:
>
> https://lore.kernel.org/r/arJoCiRM1hRbgRb5@xxxxxxxxxxxx
>
> neither of which have had any response at all. It really seems like
> there is some room for improvement in your processes here, currently
> that's three drm trees all held out of -next with the same fairly simple
> build issue. Can I suggest at least check to see if the code you are
> trying to merge is in -next, the drm merge was done after amdgpu had
> been held out of -next for several days.
I sent the PR out on Thursday and you reported the issue on Friday,
then the weekend happened. It was investigated and fixed, however
Dave reported a different stack frame warning yesterday so we are
trying to make sure that is resolved as well. In addition we've been
trying to figure out why our clang builds did not catch it in the
first place. All the patches should be available momentarily.
Alex