From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [peterz-queue:x86/ibt 1/10] vmlinux.o: warning: objtool: .export_symbol+0xc8: data relocation to !ENDBR: entry_ibpb+0x0
Date: Sat, 28 Sep 2024 15:42:48 +0800 [thread overview]
Message-ID: <202409281546.k7pYPyDV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/ibt
head: 4e155f6fbba48ed677042026d7732c6256ffa166
commit: a8cfc198458df20142631aa83f9e56deaf92ec9f [1/10] x86/cfi: Wreck things...
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20240928/202409281546.k7pYPyDV-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240928/202409281546.k7pYPyDV-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202409281546.k7pYPyDV-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> vmlinux.o: warning: objtool: .export_symbol+0xc8: data relocation to !ENDBR: entry_ibpb+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0xe8: data relocation to !ENDBR: asm_load_gs_index+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0xf8: data relocation to !ENDBR: clear_bhb_loop+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x14148: data relocation to !ENDBR: rdmsr_safe_regs+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x14158: data relocation to !ENDBR: wrmsr_safe_regs+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x14168: data relocation to !ENDBR: __sw_hweight32+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x14178: data relocation to !ENDBR: __sw_hweight64+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x2fed0: data relocation to !ENDBR: clear_page_rep+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x2fee0: data relocation to !ENDBR: clear_page_orig+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x2fef0: data relocation to !ENDBR: clear_page_erms+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x2ff00: data relocation to !ENDBR: rep_stos_alternative+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x2ff20: data relocation to !ENDBR: copy_page+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x2ff30: data relocation to !ENDBR: rep_movs_alternative+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x2ff40: data relocation to !ENDBR: __copy_user_nocache+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x30000: data relocation to !ENDBR: __get_user_1+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x30010: data relocation to !ENDBR: __get_user_2+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x30020: data relocation to !ENDBR: __get_user_4+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x30030: data relocation to !ENDBR: __get_user_8+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x30040: data relocation to !ENDBR: __get_user_nocheck_1+0x0
>> vmlinux.o: warning: objtool: .export_symbol+0x30050: data relocation to !ENDBR: __get_user_nocheck_2+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30060: data relocation to !ENDBR: __get_user_nocheck_4+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30070: data relocation to !ENDBR: __get_user_nocheck_8+0x0
vmlinux.o: warning: objtool: .export_symbol+0x300a0: data relocation to !ENDBR: memmove+0x0
vmlinux.o: warning: objtool: .export_symbol+0x300b0: data relocation to !ENDBR: memmove+0x0
vmlinux.o: warning: objtool: .export_symbol+0x300c0: data relocation to !ENDBR: memset+0x0
vmlinux.o: warning: objtool: .export_symbol+0x300d0: data relocation to !ENDBR: memset+0x0
vmlinux.o: warning: objtool: .export_symbol+0x300e0: data relocation to !ENDBR: __put_user_1+0x0
vmlinux.o: warning: objtool: .export_symbol+0x300f0: data relocation to !ENDBR: __put_user_nocheck_1+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30100: data relocation to !ENDBR: __put_user_2+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30110: data relocation to !ENDBR: __put_user_nocheck_2+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30120: data relocation to !ENDBR: __put_user_4+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30130: data relocation to !ENDBR: __put_user_nocheck_4+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30140: data relocation to !ENDBR: __put_user_8+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30150: data relocation to !ENDBR: __put_user_nocheck_8+0x0
vmlinux.o: warning: objtool: .export_symbol+0x30470: data relocation to !ENDBR: entry_untrain_ret+0x0
objdump-func vmlinux.o .export_symbol:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-09-28 7:43 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=202409281546.k7pYPyDV-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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.