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,
Borislav Petkov <bp@suse.de>,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: vmlinux.o: warning: objtool: xen_hypercall_iret+0x0: RET before UNTRAIN
Date: Sat, 8 Apr 2023 05:18:35 +0800 [thread overview]
Message-ID: <202304080538.j5G6h1AB-lkp@intel.com> (raw)
Hi Peter,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f2afccfefe7be1f7346564fe619277110d341f9b
commit: a09a6e2399ba0595c3042b3164f3ca68a3cff33e objtool: Add entry UNRET validation
date: 10 months ago
config: x86_64-randconfig-a012-20221205 (https://download.01.org/0day-ci/archive/20230408/202304080538.j5G6h1AB-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a09a6e2399ba0595c3042b3164f3ca68a3cff33e
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout a09a6e2399ba0595c3042b3164f3ca68a3cff33e
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 olddefconfig
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304080538.j5G6h1AB-lkp@intel.com/
All warnings (new ones prefixed by >>):
ld: warning: arch/x86/lib/retpoline.o: missing .note.GNU-stack section implies executable stack
ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
vmlinux.o: warning: objtool: cdce925_regmap_i2c_write+0xdb: stack state mismatch: cfa1=4+120 cfa2=5+40
>> vmlinux.o: warning: objtool: xen_hypercall_iret+0x0: RET before UNTRAIN
objdump-func vmlinux.o xen_hypercall_iret:
0000 00000000000002e0 <xen_hypercall_iret>:
0000 2e0: c3 ret
0001 2e1: cc int3
0002 2e2: cc int3
0003 2e3: cc int3
0004 2e4: cc int3
0005 2e5: cc int3
0006 2e6: cc int3
0007 2e7: cc int3
0008 2e8: cc int3
0009 2e9: cc int3
000a 2ea: cc int3
000b 2eb: cc int3
000c 2ec: cc int3
000d 2ed: cc int3
000e 2ee: cc int3
000f 2ef: cc int3
0010 2f0: cc int3
0011 2f1: cc int3
0012 2f2: cc int3
0013 2f3: cc int3
0014 2f4: cc int3
0015 2f5: cc int3
0016 2f6: cc int3
0017 2f7: cc int3
0018 2f8: cc int3
0019 2f9: cc int3
001a 2fa: cc int3
001b 2fb: cc int3
001c 2fc: cc int3
001d 2fd: cc int3
001e 2fe: cc int3
001f 2ff: cc int3
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-04-07 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 21:18 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-06 7:00 kernel test robot
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=202304080538.j5G6h1AB-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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®