From: Nathan Chancellor <nathan@kernel.org>
To: Calvin Owens <calvin@wbinvd.org>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org,
Charlene Liu <charlene.liu@amd.com>,
Ovidiu Bunea <ovidiu.bunea@amd.com>,
Alex Hung <alex.hung@amd.com>,
Dan Wheeler <daniel.wheeler@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
Rodrigo Siqueira <siqueira@igalia.com>,
Christian Koenig <christian.koenig@amd.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
llvm@lists.linux.dev
Subject: Re: [PATCH v2] drm/amd/display: Fix uninitialized variable use which breaks full LTO
Date: Thu, 12 Mar 2026 13:37:40 -0700 [thread overview]
Message-ID: <20260312203740.GA2747807@ax162> (raw)
In-Reply-To: <abL0PlD1FDnfrX4o@mozart.vkv.me>
On Thu, Mar 12, 2026 at 10:13:34AM -0700, Calvin Owens wrote:
> Commit e1b385726f7f ("drm/amd/display: Add additional checks for PSP
> footer size") introduced a use of an uninitialized stack variable
> in dm_dmub_sw_init() (region_params.bss_data_size).
>
> Interestingly, this seems to cause no issue on normal kernels. But when
> full LTO is enabled, it causes the compiler to "optimize" out huge
> swaths of amdgpu initialization code, and the driver is unusable:
>
> amdgpu 0000:03:00.0: [drm] Loading DMUB firmware via PSP: version=0x07002F00
> amdgpu 0000:03:00.0: sw_init of IP block <dm> failed 5
> amdgpu 0000:03:00.0: amdgpu_device_ip_init failed
> amdgpu 0000:03:00.0: Fatal error during GPU init
>
> It surprises me that neither gcc nor clang emit a warning about this: I
> only found it by bisecting the LTO breakage.
>
> Fix by using the bss_data_size field from fw_meta_info_params, as was
> presumably intended.
>
> Fixes: e1b385726f7f ("drm/amd/display: Add additional checks for PSP footer size")
> Signed-off-by: Calvin Owens <calvin@wbinvd.org>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
> Changes in v2:
> * Use fw_meta_info_params.bss_data_size instead of repeating the load
> from the payload header field [Nathan]
>
> drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index b3d6f2cd8ab6..0d1c772ef713 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -2553,9 +2553,9 @@ static int dm_dmub_sw_init(struct amdgpu_device *adev)
> fw_meta_info_params.bss_data_size = le32_to_cpu(hdr->bss_data_bytes);
> fw_meta_info_params.fw_inst_const = adev->dm.dmub_fw->data +
> le32_to_cpu(hdr->header.ucode_array_offset_bytes) +
> PSP_HEADER_BYTES_256;
> - fw_meta_info_params.fw_bss_data = region_params.bss_data_size ? adev->dm.dmub_fw->data +
> + fw_meta_info_params.fw_bss_data = fw_meta_info_params.bss_data_size ? adev->dm.dmub_fw->data +
> le32_to_cpu(hdr->header.ucode_array_offset_bytes) +
> le32_to_cpu(hdr->inst_const_bytes) : NULL;
> fw_meta_info_params.custom_psp_footer_size = 0;
>
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2026-03-12 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 4:24 [REGRESSION][PATCH] drm/amd/display: Fix uninitialized variable which breaks full LTO Calvin Owens
2026-03-10 5:54 ` Calvin Owens
2026-03-12 8:02 ` Nathan Chancellor
2026-03-12 16:15 ` Calvin Owens
2026-03-12 17:13 ` [PATCH v2] drm/amd/display: Fix uninitialized variable use " Calvin Owens
2026-03-12 20:31 ` Harry Wentland
2026-03-12 20:37 ` Nathan Chancellor [this message]
2026-03-13 3:56 ` Claude review: [PATCH] drm/amd/display: Fix uninitialized variable " Claude Code Review Bot
2026-03-13 3:56 ` Claude Code Review Bot
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=20260312203740.GA2747807@ax162 \
--to=nathan@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=calvin@wbinvd.org \
--cc=charlene.liu@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.wheeler@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ovidiu.bunea@amd.com \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
/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