From: "Arnd Bergmann" <arnd@arndb.de>
To: "Josh Poimboeuf" <jpoimboe@kernel.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
"Nathan Chancellor" <nathan@kernel.org>
Subject: Re: clang/objtool failures on linux-next
Date: Fri, 06 Mar 2026 22:02:54 +0100 [thread overview]
Message-ID: <fdc0a032-a803-4649-9d66-32f118f118bf@app.fastmail.com> (raw)
In-Reply-To: <crbu3syyqcoqsjbddbbldm4nxavkrqwr3giscxkc35un7xpwt6@dtfvj5kjxhp5>
On Fri, Mar 6, 2026, at 19:29, Josh Poimboeuf wrote:
> On Fri, Mar 06, 2026 at 09:31:02AM -0800, Josh Poimboeuf wrote:
>> On Fri, Mar 06, 2026 at 01:41:59PM +0100, Arnd Bergmann wrote:
>>
>> Thanks, I'll post a fix for the 1st one right now (haven't looked at the
>> stack overflow yet).
>
> Both fixes posted now:
>
> https://lore.kernel.org/240e6a172cc73292499334a3724d02ccb3247fc7.1772818491.git.jpoimboe@kernel.org
> https://lore.kernel.org/8b97f62d083457f3b0a29a424275f7957dd3372f.1772821683.git.jpoimboe@kernel.org
Thanks a lot, that was quick!
I've applied both to my randconfig tree now and verified that
both issues are addressed in the full build. There is still
the question of the 0xAE77DEF6_defconfig causing an incredibly
long compile time (minutes!) for the one file when using clang.
I've added Nathan to Cc in case he is motivated to try to
reproduce this.
FWIW, this is the current set of objtool warnings that I get that
don't cause the build to fail:
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.o: warning: objtool: amdgpu_cs_parser_bos+0x723: unreachable instruction
drivers/gpu/drm/msm/msm.o: warning: objtool: msm_gem_vm_close+0x1cf: unreachable instruction
drivers/gpu/drm/panthor/panthor.o: warning: objtool: panthor_ioctl_vm_bind+0x32b: __stack_chk_fail() missing __noreturn in .c/.h or NORETURN() in noreturns.h
drivers/gpu/drm/panthor/panthor.o: warning: objtool: panthor_ioctl_vm_bind_async+0x285: unreachable instruction
drivers/gpu/drm/panthor/panthor_drv.o: warning: objtool: panthor_ioctl_vm_bind+0x2df: unreachable instruction
drivers/gpu/drm/xe/xe_bo.o: warning: objtool: xe_bo_create_pin_map_at_novm+0x11d: unreachable instruction
drivers/iio/imu/bmi160/bmi160_core.o: warning: objtool: bmi160_setup_irq() falls through to next function __cfi_bmi160_core_runtime_resume()
kernel/bpf/core.o: warning: objtool: ___bpf_prog_run+0x217: sibling call from callable instruction with modified stack frame
sound/soc/codecs/wcd9335.o: warning: objtool: wcd9335_slimbus_irq() falls through to next function __cfi_wcd9335_set_channel_map()
vmlinux.o: warning: objtool: ___bpf_prog_run+0x1d4: sibling call from callable instruction with modified stack frame
vmlinux.o: warning: objtool: hdmi_power_on_full.isra.0+0xd6: hdmi_pll_compute() missing __noreturn in .c/.h or NORETURN() in noreturns.h
If you want to investigate those, I can send you the configs and/or
object files for these as well.
Arnd
next prev parent reply other threads:[~2026-03-06 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 12:41 clang/objtool failures on linux-next Arnd Bergmann
2026-03-06 17:30 ` Josh Poimboeuf
2026-03-06 18:29 ` Josh Poimboeuf
2026-03-06 21:02 ` Arnd Bergmann [this message]
2026-03-06 21:17 ` Josh Poimboeuf
2026-03-06 22:04 ` Arnd Bergmann
2026-03-07 1:35 ` Josh Poimboeuf
2026-03-09 21:15 ` Nathan Chancellor
2026-03-09 21:27 ` Arnd Bergmann
2026-03-07 1:37 ` Josh Poimboeuf
2026-03-06 23:25 ` Nathan Chancellor
2026-03-16 21:27 ` Arnd Bergmann
2026-03-17 0:29 ` Josh Poimboeuf
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=fdc0a032-a803-4649-9d66-32f118f118bf@app.fastmail.com \
--to=arnd@arndb.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
/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