From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: vmlinux.o: warning: objtool: handle_bug+0x4: call to kmsan_unpoison_entry_regs() leaves .noinstr.text section
Date: Mon, 20 Mar 2023 19:41:14 +0800 [thread overview]
Message-ID: <202303201934.LNi7ToIP-lkp@intel.com> (raw)
CC: linux-kernel@vger.kernel.org
TO: Alexander Potapenko <glider@google.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
Hi Alexander,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: e8d018dd0257f744ca50a729e3d042cf2ec9da65
commit: ba54d194f8daad8943802d6dfe06e205f882c391 x86/traps: avoid KMSAN bugs originating from handle_bug()
date: 4 months ago
config: x86_64-buildonly-randconfig-r005-20230320 (https://download.01.org/0day-ci/archive/20230320/202303201934.LNi7ToIP-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba54d194f8daad8943802d6dfe06e205f882c391
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout ba54d194f8daad8943802d6dfe06e205f882c391
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross 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/202303201934.LNi7ToIP-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> vmlinux.o: warning: objtool: handle_bug+0x4: call to kmsan_unpoison_entry_regs() leaves .noinstr.text section
objdump-func vmlinux.o handle_bug:
0000 0000000000000380 <handle_bug>:
0000 380: 53 push %rbx
0001 381: 48 89 fb mov %rdi,%rbx
0004 384: e8 00 00 00 00 call 389 <handle_bug+0x9> 385: R_X86_64_PLT32 kmsan_unpoison_entry_regs-0x4
0009 389: 48 8b 83 80 00 00 00 mov 0x80(%rbx),%rax
0010 390: 48 b9 00 f0 ff ff ff 7f 00 00 movabs $0x7ffffffff000,%rcx
001a 39a: 48 39 c8 cmp %rcx,%rax
001d 39d: 72 41 jb 3e0 <handle_bug+0x60>
001f 39f: 0f b7 00 movzwl (%rax),%eax
0022 3a2: 3d 0f 0b 00 00 cmp $0xb0f,%eax
0027 3a7: 75 37 jne 3e0 <handle_bug+0x60>
0029 3a9: 90 nop
002a 3aa: f6 83 91 00 00 00 02 testb $0x2,0x91(%rbx)
0031 3b1: 74 01 je 3b4 <handle_bug+0x34>
0033 3b3: fb sti
0034 3b4: 48 8b bb 80 00 00 00 mov 0x80(%rbx),%rdi
003b 3bb: 48 89 de mov %rbx,%rsi
003e 3be: e8 00 00 00 00 call 3c3 <handle_bug+0x43> 3bf: R_X86_64_PLT32 report_bug-0x4
0043 3c3: 83 f8 01 cmp $0x1,%eax
0046 3c6: 0f 94 c0 sete %al
0049 3c9: 75 08 jne 3d3 <handle_bug+0x53>
004b 3cb: 48 83 83 80 00 00 00 02 addq $0x2,0x80(%rbx)
0053 3d3: f6 83 91 00 00 00 02 testb $0x2,0x91(%rbx)
005a 3da: 74 01 je 3dd <handle_bug+0x5d>
005c 3dc: fa cli
005d 3dd: 90 nop
005e 3de: 5b pop %rbx
005f 3df: c3 ret
0060 3e0: 31 c0 xor %eax,%eax
0062 3e2: 5b pop %rbx
0063 3e3: c3 ret
0064 3e4: 66 2e 0f 1f 84 00 00 00 00 00 cs nopw 0x0(%rax,%rax,1)
006e 3ee: 66 2e 0f 1f 84 00 00 00 00 00 cs nopw 0x0(%rax,%rax,1)
0078 3f8: 0f 1f 84 00 00 00 00 00 nopl 0x0(%rax,%rax,1)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-03-20 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 11:41 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 20:20 vmlinux.o: warning: objtool: handle_bug+0x4: call to kmsan_unpoison_entry_regs() leaves .noinstr.text section 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=202303201934.LNi7ToIP-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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.