All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Borislav Petkov <bp@suse.de>, kernel test robot <lkp@intel.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to memset() leaves .noinstr.text section
Date: Wed, 27 Oct 2021 15:26:22 +0800	[thread overview]
Message-ID: <f7962977-52a1-b18f-7485-9d2247de5703@intel.com> (raw)
In-Reply-To: <YXe7AnMmiWXk36NC@zn.tnic>



On 10/26/2021 4:23 PM, Borislav Petkov wrote:
> Hi,
> 
> On Tue, Oct 26, 2021 at 04:16:21PM +0800, kernel test robot wrote:
>> 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
> 
> if you have the technical capability to ignore all noinstr warnings
> coming from the mce code, please do so.
> 
> I have a patchset to address that but more important work preempts me
> constantly from cleaning it up and sending it out properly. ;-\
> 

Hi Borislav,

Thanks for the feedback, We have ignored these warnings from mce.

Best Regards,
Rong Chen

WARNING: multiple messages have this Message-ID (diff)
From: Chen, Rong A <rong.a.chen@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to memset() leaves .noinstr.text section
Date: Wed, 27 Oct 2021 15:26:22 +0800	[thread overview]
Message-ID: <f7962977-52a1-b18f-7485-9d2247de5703@intel.com> (raw)
In-Reply-To: <YXe7AnMmiWXk36NC@zn.tnic>

[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]



On 10/26/2021 4:23 PM, Borislav Petkov wrote:
> Hi,
> 
> On Tue, Oct 26, 2021 at 04:16:21PM +0800, kernel test robot wrote:
>> 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
> 
> if you have the technical capability to ignore all noinstr warnings
> coming from the mce code, please do so.
> 
> I have a patchset to address that but more important work preempts me
> constantly from cleaning it up and sending it out properly. ;-\
> 

Hi Borislav,

Thanks for the feedback, We have ignored these warnings from mce.

Best Regards,
Rong Chen

  reply	other threads:[~2021-10-27  7:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  8:16 vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to memset() leaves .noinstr.text section kernel test robot
2021-10-26  8:16 ` kernel test robot
2021-10-26  8:23 ` Borislav Petkov
2021-10-26  8:23   ` Borislav Petkov
2021-10-27  7:26   ` Chen, Rong A [this message]
2021-10-27  7:26     ` Chen, Rong A
2022-01-19 18:22   ` Jakub Kicinski
2022-01-19 18:22     ` Jakub Kicinski
2022-01-19 18:34     ` Borislav Petkov
2022-01-19 18:34       ` Borislav Petkov
2022-01-19 18:40       ` Jakub Kicinski
2022-01-19 18:40         ` Jakub Kicinski
2022-01-19 19:15         ` Jakub Kicinski
2022-01-19 19:15           ` Jakub Kicinski
2022-01-19 20:30           ` Borislav Petkov
2022-01-19 20:30             ` Borislav Petkov
2022-01-19 20:37             ` Jakub Kicinski
2022-01-19 20:37               ` Jakub Kicinski
2022-01-19 21:16               ` Borislav Petkov
2022-01-19 21:16                 ` Borislav Petkov
2022-01-19 22:57                 ` Jakub Kicinski
2022-01-19 22:57                   ` Jakub Kicinski
2022-01-19 23:17                   ` Borislav Petkov
2022-01-19 23:17                     ` Borislav Petkov
2022-01-19 23:32                     ` Jakub Kicinski
2022-01-19 23:32                       ` Jakub Kicinski
2022-01-31 12:06                       ` Borislav Petkov
2022-01-31 12:06                         ` Borislav Petkov
2022-01-31 16:56                         ` Jakub Kicinski
2022-01-31 16:56                           ` Jakub Kicinski
2022-02-01 13:05                           ` Borislav Petkov
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=f7962977-52a1-b18f-7485-9d2247de5703@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=bp@suse.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --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 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.