From: "Arnd Bergmann" <arnd@arndb.de>
To: "Peter Zijlstra" <peterz@infradead.org>,
"Josh Poimboeuf" <jpoimboe@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: clang/objtool failures on linux-next
Date: Mon, 16 Mar 2026 22:27:44 +0100 [thread overview]
Message-ID: <cefefdd1-7b82-406d-8ff4-e4b167e45ee6@app.fastmail.com> (raw)
In-Reply-To: <90956545-2066-46e3-b547-10c884582eb0@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
I've found two more objtool related build failures on today's linux-next.
See attachment for .config and object files.
==> build/x86/0x8F5E6B2F_defconfig/log <==
mm/memory.o: warning: objtool: folio_zero_user+0x69a: undefined stack state
mm/memory.o: error: objtool: folio_zero_user+0x69a: unknown CFA base reg -1
make[5]: *** [/home/arnd/arm-soc/scripts/Makefile.build:279: mm/memory.o] Error 255
==> build/x86/0xEC8A503_defconfig/log <==
vmlinux.o: warning: objtool: ___bpf_prog_run+0x202: sibling call from callable instruction with modified stack frame
vmlinux.o: warning: objtool: __x64_sys_get_mempolicy+0x1705: stack state mismatch: cfa1=4+288 cfa2=4+80
vmlinux.o: error: objtool: vmw_host_printf+0xd: unknown CFA base reg 0
make[4]: *** [/home/arnd/arm-soc/scripts/Makefile.vmlinux_o:76: vmlinux.o] Error 255
Arnd
[-- Attachment #2: objtool-failures-next-20260316.tar.gz --]
[-- Type: application/gzip, Size: 884136 bytes --]
next prev parent reply other threads:[~2026-03-16 21:30 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
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 [this message]
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=cefefdd1-7b82-406d-8ff4-e4b167e45ee6@app.fastmail.com \
--to=arnd@arndb.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.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