LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>, Miroslav Benes <mbenes@suse.cz>
Subject: Re: vmlinux.o: warning: objtool: noist_exc_machine_check()+0x93: call to __sanitizer_cov_trace_pc() leaves .noinstr.text section
Date: Fri, 3 Sep 2021 19:22:25 +0200	[thread overview]
Message-ID: <YTJZzVrutm4yZAzi@zn.tnic> (raw)
In-Reply-To: <202108221656.2tMcBD2a-lkp@intel.com>

On Sun, Aug 22, 2021 at 04:54:06PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   9ff50bf2f2ff5fab01cac26d8eed21a89308e6ef
> commit: bcb1b6ff39da7e8a6a986eb08126fba2b5e13c32 objtool: Correctly handle retpoline thunk calls
> date:   5 months ago
> config: x86_64-buildonly-randconfig-r003-20210822 (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=bcb1b6ff39da7e8a6a986eb08126fba2b5e13c32
>         git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>         git fetch --no-tags linus master
>         git checkout bcb1b6ff39da7e8a6a986eb08126fba2b5e13c32
>         # 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: mce_wrmsrl.constprop.0()+0x6b: call to __sanitizer_cov_trace_pc() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: do_machine_check()+0xb14: call to queue_task_work() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: exc_machine_check()+0xdb: call to __sanitizer_cov_trace_pc() leaves .noinstr.text section
> >> vmlinux.o: warning: objtool: noist_exc_machine_check()+0x93: call to __sanitizer_cov_trace_pc() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: __context_tracking_enter()+0x95: call to __sanitizer_cov_trace_pc() leaves .noinstr.text section
>    vmlinux.o: warning: objtool: __context_tracking_exit()+0x42: call to __sanitizer_cov_trace_pc() leaves .noinstr.text section
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

https://lkml.kernel.org/r/YTHpmGmlo9N%2B1Rs7@hirez.programming.kicks-ass.net

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

      reply	other threads:[~2021-09-03 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22  8:54 kernel test robot
2021-09-03 17:22 ` Borislav Petkov [this message]

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=YTJZzVrutm4yZAzi@zn.tnic \
    --to=bp@suse.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mbenes@suse.cz \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --subject='Re: vmlinux.o: warning: objtool: noist_exc_machine_check()+0x93: call to __sanitizer_cov_trace_pc() leaves .noinstr.text section' \
    /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

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).