From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Borislav Petkov <bp@suse.de>
Subject: vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to memset() leaves .noinstr.text section
Date: Tue, 26 Oct 2021 16:16:21 +0800 [thread overview]
Message-ID: <202110261614.Bt8EM6Nj-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3906fe9bb7f1a2c8667ae54e967dc8690824f4ea
commit: 7bb39313cd6239e7eb95198950a02b4ad2a08316 x86/mce: Make mce_timed_out() identify holdout CPUs
date: 10 months ago
config: x86_64-buildonly-randconfig-r006-20211022 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7bb39313cd6239e7eb95198950a02b4ad2a08316
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 7bb39313cd6239e7eb95198950a02b4ad2a08316
# save the attached .config to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to memset() leaves .noinstr.text section
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37142 bytes --]
next reply other threads:[~2021-10-26 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 8:16 kernel test robot [this message]
2021-10-26 8:23 ` vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to memset() leaves .noinstr.text section Borislav Petkov
2021-10-27 7:26 ` [kbuild-all] " Chen, Rong A
2022-01-19 18:22 ` Jakub Kicinski
2022-01-19 18:34 ` Borislav Petkov
2022-01-19 18:40 ` Jakub Kicinski
2022-01-19 19:15 ` Jakub Kicinski
2022-01-19 20:30 ` Borislav Petkov
2022-01-19 20:37 ` Jakub Kicinski
2022-01-19 21:16 ` Borislav Petkov
2022-01-19 22:57 ` Jakub Kicinski
2022-01-19 23:17 ` Borislav Petkov
2022-01-19 23:32 ` Jakub Kicinski
2022-01-31 12:06 ` Borislav Petkov
2022-01-31 16:56 ` Jakub Kicinski
2022-02-01 13:05 ` Borislav Petkov
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=202110261614.Bt8EM6Nj-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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;
as well as URLs for NNTP newsgroup(s).