From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: vmlinux.o: warning: objtool: kvm_spurious_fault()+0x22: call to ftrace_likely_update() leaves .noinstr.text section
Date: Sat, 13 Nov 2021 08:31:15 +0100 [thread overview]
Message-ID: <YY9pw6wrKsY5CrOo@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <202111131049.j3jDJJap-lkp@intel.com>
On Sat, Nov 13, 2021 at 10:48:52AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 66f4beaa6c1d28161f534471484b2daa2de1dce0
> commit: 63b3f96e1a989846a5a521d4fbef4bc86406929d kvm: Select SCHED_INFO instead of TASK_DELAY_ACCT
> date: 6 months ago
> config: x86_64-buildonly-randconfig-r002-20211009 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63b3f96e1a989846a5a521d4fbef4bc86406929d
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 63b3f96e1a989846a5a521d4fbef4bc86406929d
> # save the attached .config to linux build tree
> mkdir build_dir
> make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
> >> vmlinux.o: warning: objtool: kvm_spurious_fault()+0x22: call to ftrace_likely_update() leaves .noinstr.text section
> >> vmlinux.o: warning: objtool: vmx_update_host_rsp()+0x34: call to ftrace_likely_update() leaves .noinstr.text section
Yeah, that's CONFIG_TRACE_BRANCH_PROFILING and it is broken. It will
eventually explode once we push the PTI CR3 switcheroo into C due to
trying to access kernel data before kernel address space is mapped.
prev parent reply other threads:[~2021-11-13 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 2:48 kernel test robot
2021-11-13 7:31 ` 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=YY9pw6wrKsY5CrOo@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®