From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, "Borislav Petkov (AMD)" <bp@alien8.de>
Subject: [tip:x86/urgent 8/15] arch/x86/lib/retpoline.o: warning: objtool: srso_untrain_ret+0xd: call without frame pointer save/setup
Date: Thu, 17 Aug 2023 01:17:06 +0800 [thread overview]
Message-ID: <202308170133.1Ix5PpIZ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
head: d80c3c9de067e08498d9bbfef7ab0b716fe4cc05
commit: 4ae68b26c3ab5a82aa271e6e9fc9b1a06e1d6b40 [8/15] objtool/x86: Fix SRSO mess
config: x86_64-randconfig-x015-20230816 (https://download.01.org/0day-ci/archive/20230817/202308170133.1Ix5PpIZ-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230817/202308170133.1Ix5PpIZ-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/202308170133.1Ix5PpIZ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/lib/retpoline.o: warning: objtool: srso_untrain_ret+0xd: call without frame pointer save/setup
objdump-func vmlinux.o srso_untrain_ret:
0000 0000000000000000 <srso_untrain_ret_alias>:
0000 0: 66 90 xchg %ax,%ax
0002 2: 0f ae e8 lfence
0005 5: e9 00 00 00 00 jmp a <__pcpu_unique_p4_running> 6: R_X86_64_PLT32 __x86_return_thunk-0x4
0000 00000000000000be <srso_untrain_ret>:
0000 be: 48 rex.W
0001 bf: b8 .byte 0xb8
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-16 17:18 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=202308170133.1Ix5PpIZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=x86@kernel.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 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®