From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: vmlinux.o: warning: objtool: .altinstr_replacement+0x5e4: call without frame pointer save/setup
Date: Mon, 16 May 2022 23:02:32 +0800 [thread overview]
Message-ID: <202205162203.X9ZMQm2k-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: linux-kernel@vger.kernel.org
TO: Peter Zijlstra <peterz@infradead.org>
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 42226c989789d8da4af1de0c31070c96726d990c
commit: ed53a0d971926e484d86cce617ec02a7ee85c3fe x86/alternative: Use .ibt_endbr_seal to seal indirect calls
date: 9 weeks ago
config: x86_64-randconfig-a005-20220516 (https://download.01.org/0day-ci/archive/20220516/202205162203.X9ZMQm2k-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 853fa8ee225edf2d0de94b0dcbd31bea916e825e)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed53a0d971926e484d86cce617ec02a7ee85c3fe
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout ed53a0d971926e484d86cce617ec02a7ee85c3fe
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross 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: ibt_selftest()+0x14: sibling call from callable instruction with modified stack frame
>> vmlinux.o: warning: objtool: .altinstr_replacement+0x5e4: call without frame pointer save/setup
vmlinux.o: warning: objtool: do_syscall_64()+0x9f: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: do_int80_syscall_32()+0xb0: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: __do_fast_syscall_32()+0x108: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: fixup_bad_iret()+0x2a: call to memset() leaves .noinstr.text section
vmlinux.o: warning: objtool: in_task_stack()+0x14: call to task_stack_page() leaves .noinstr.text section
vmlinux.o: warning: objtool: in_entry_stack()+0x11: call to cpu_entry_stack() leaves .noinstr.text section
vmlinux.o: warning: objtool: enter_from_user_mode()+0x30: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x39: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x30: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x30: call to __kcsan_check_access() leaves .noinstr.text section
vmlinux.o: warning: objtool: ibt_selftest()+0x1e: return with modified stack frame
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-16 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202205162203.X9ZMQm2k-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
/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