From: kernel test robot <lkp@intel.com>
To: Ben Hutchings <bwh@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [stable:linux-4.14.y 3640/5153] arch/x86/entry/.tmp_entry_64.o: warning: objtool: .entry.text+0x888: unreachable instruction
Date: Thu, 24 Aug 2023 20:31:15 +0800 [thread overview]
Message-ID: <202308242012.o6WHSxJT-lkp@intel.com> (raw)
Hi Ben,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y
head: 80b73c056d2076d12f9e50c753bb440fc79f30c9
commit: 369e65def1a82aba54b377b6899b1bb5099ef838 [3640/5153] Revert "x86/speculation: Change FILL_RETURN_BUFFER to work with objtool"
config: x86_64-randconfig-073-20230824 (https://download.01.org/0day-ci/archive/20230824/202308242012.o6WHSxJT-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce: (https://download.01.org/0day-ci/archive/20230824/202308242012.o6WHSxJT-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/202308242012.o6WHSxJT-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/x86/entry/entry_64.S: Assembler messages:
arch/x86/entry/entry_64.S:1672: Warning: no instruction mnemonic suffix given and no register operands; using default for `sysret'
>> arch/x86/entry/.tmp_entry_64.o: warning: objtool: .entry.text+0x888: unreachable instruction
objdump-func vmlinux.o .entry.text:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-24 12:31 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=202308242012.o6WHSxJT-lkp@intel.com \
--to=lkp@intel.com \
--cc=bwh@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=oe-kbuild-all@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 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.