From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Voytik <voytikd@gmail.com>
Cc: glider@google.com, jpoimboe@kernel.org,
kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] CONFIG_KMSAN breaks objtool and building of the kernel
Date: Wed, 17 Jun 2026 09:48:31 +0200 [thread overview]
Message-ID: <20260617074831.GL42921@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAAX90H2_RPnZL_dFYN7cQF6yt-wAweKKSx2=6e2aZ0kv+Pm+NQ@mail.gmail.com>
On Wed, Jun 17, 2026 at 12:14:26AM +0200, Dmitry Voytik wrote:
> Enabling CONFIG_KMSAN=y triggers the following build error:
> make LLVM=1 -j(nproc)
> SYNC include/config/auto.conf
> DESCEND objtool
> INSTALL libsubcmd_headers
> LD vmlinux.o
> vmlinux.o: warning: objtool: intel_pt_interrupt+0xde9: undefined stack state
> vmlinux.o: warning: objtool: folio_zero_user+0x7cc: undefined stack state
> vmlinux.o: error: objtool: intel_pt_interrupt+0xde4: unknown cfa base reg -1
> make[2]: *** [scripts/Makefile.vmlinux_o:76: vmlinux.o] Error 255
> make[2]: *** Deleting file 'vmlinux.o'
>
> ↪ git log --oneline | head -n1
> 062871f1371b (HEAD -> master, origin/master, origin/HEAD) Merge tag
> 'pinctrl-v7.1-3' of
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
>
> ↪ clang --version
> clang version 22.1.6
> Target: x86_64-pc-linux-gnu
>
> Please let me know if you need my .config (basically, it's the default
> Arch Linux config + make oldconfg)
Using v7.1-2765-g6b5a2b7d9bc1, clang-22.1.0 (debian) and defconfig+KMSAN, I
cannot reproduce :/
prev parent reply other threads:[~2026-06-17 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 22:14 [BUG] CONFIG_KMSAN breaks objtool and building of the kernel Dmitry Voytik
2026-06-17 7:48 ` Peter Zijlstra [this message]
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=20260617074831.GL42921@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=glider@google.com \
--cc=jpoimboe@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=voytikd@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.