From: Sean Christopherson <seanjc@google.com>
To: Calvin Owens <calvin@wbinvd.org>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
tglx@kernel.org, vishal.l.verma@intel.com, zhao1.liu@intel.com,
binbin.wu@linxu.intel.com, x86@kernel.org, kvm@vger.kernel.org,
nathan@kernel.org
Subject: Re: New "no-cfi indirect call!" build failure on 7.1-rc5
Date: Tue, 26 May 2026 06:45:28 -0700 [thread overview]
Message-ID: <ahWj-P_1uOlYku4m@google.com> (raw)
In-Reply-To: <ahSMMAUQ83P-NeOi@mozart.vkv.me>
On Mon, May 25, 2026, Calvin Owens wrote:
> Hello all,
>
> I'm seeing build failures with the attached kconfig on 7.1-rc5:
>
> running 'make' '-skj32' 'oldconfig' 'tar-pkg' 'LLVM=/home/calvinow/llvm-22.1.5/bin/'
> vmlinux.o: error: objtool: idt_do_interrupt_irqoff+0xe: no-cfi indirect call!
>
> It bisects down to commit 0701c9e17bd903d95b2ddf7dd2e1d8be5027f331:
>
> Author: Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Fri May 8 11:18:29 2026 +0200
> Commit: Thomas Gleixner <tglx@kernel.org>
> CommitDate: Tue May 19 20:25:51 2026 +0200
>
> x86/kvm/vmx: Move IRQ/NMI dispatch from KVM into x86 core
>
> Nathan noticed it last week in -next:
>
> https://lore.kernel.org/all/20260520230621.GA706311@ax162/
>
> You can reproduce my LLVM with this, in case it matters:
> https://github.com/jcalvinowens/kernel-testing/blob/master/scripts/build-llvm.sh
Peter is on it: https://lore.kernel.org/all/20260526090631.GA4149641@noisy.programming.kicks-ass.net
prev parent reply other threads:[~2026-05-26 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 17:51 New "no-cfi indirect call!" build failure on 7.1-rc5 Calvin Owens
2026-05-26 13:45 ` Sean Christopherson [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=ahWj-P_1uOlYku4m@google.com \
--to=seanjc@google.com \
--cc=binbin.wu@linxu.intel.com \
--cc=calvin@wbinvd.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=x86@kernel.org \
--cc=zhao1.liu@intel.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.