From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [peterz-queue:objtool/retpoline 15/15] arch/x86/kernel/ftrace_64.o: warning: objtool: can't find symbol containing .altinstr_replacement+0x0
Date: Sat, 20 Mar 2021 12:30:57 +0800 [thread overview]
Message-ID: <202103201248.EnraAun3-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
Hi Peter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git objtool/retpoline
head: 72260c7ae8c8e1265dbd20213ce67ddfaf76df8e
commit: 72260c7ae8c8e1265dbd20213ce67ddfaf76df8e [15/15] objtool,x86: Rewrite retpoline thunk calls
config: x86_64-allyesconfig (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/peterz/queue.git/commit/?id=72260c7ae8c8e1265dbd20213ce67ddfaf76df8e
git remote add peterz-queue https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git
git fetch --no-tags peterz-queue objtool/retpoline
git checkout 72260c7ae8c8e1265dbd20213ce67ddfaf76df8e
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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 >>):
>> arch/x86/kernel/ftrace_64.o: warning: objtool: can't find symbol containing .altinstr_replacement+0x0
>> arch/x86/kernel/ftrace_64.o: warning: objtool: elf_create_reloc: alt_instr::instr_offset
>> arch/x86/kernel/ftrace_64.o: warning: objtool: elf_add_alternative
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 65484 bytes --]
reply other threads:[~2021-03-20 4:30 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=202103201248.EnraAun3-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.