All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: kernel test robot <lkp@intel.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to memset() leaves .noinstr.text section
Date: Wed, 19 Jan 2022 10:40:17 -0800	[thread overview]
Message-ID: <20220119104017.31e5ecc7@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <YehZsGAqgd3tJyDV@zn.tnic>

On Wed, 19 Jan 2022 19:34:24 +0100 Borislav Petkov wrote:
> On Wed, Jan 19, 2022 at 10:22:50AM -0800, Jakub Kicinski wrote:
> > I was hoping that 5.17 would fix this but I just merged Linus's tree
> > with netdev today and the warnings are still there :(  
> 
> Hmm, weird. The set which is supposed to address this got merged last
> week:
> 
> 7e740ae63504 ("Merge tag 'ras_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
> 
> How exactly can I reproduce what you're seeing?
> 
> I need to merge which commit into which branch and then use which
> .config to reproduce?

allmodconfig 

Merge: 1d1df41c5a33 ff9fc0a31d85

1d1df41c5a33 is linux/master 
ff9fc0a31d85 is
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git master

I see:

vmlinux.o: warning: objtool: mce_start()+0x5e: call to __kasan_check_write() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_gather_info()+0x5f: call to v8086_mode.isra.1() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_read_aux()+0x8a: call to mca_msr_reg() leaves .noinstr.text section
vmlinux.o: warning: objtool: do_machine_check()+0x196: call to mce_no_way_out() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_severity_amd.constprop.1()+0xd1: call to mce_severity_amd_smca.isra.0() leaves .noinstr.text section

Let me try again with a clean check out.

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
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, 19 Jan 2022 10:40:17 -0800	[thread overview]
Message-ID: <20220119104017.31e5ecc7@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <YehZsGAqgd3tJyDV@zn.tnic>

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

On Wed, 19 Jan 2022 19:34:24 +0100 Borislav Petkov wrote:
> On Wed, Jan 19, 2022 at 10:22:50AM -0800, Jakub Kicinski wrote:
> > I was hoping that 5.17 would fix this but I just merged Linus's tree
> > with netdev today and the warnings are still there :(  
> 
> Hmm, weird. The set which is supposed to address this got merged last
> week:
> 
> 7e740ae63504 ("Merge tag 'ras_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
> 
> How exactly can I reproduce what you're seeing?
> 
> I need to merge which commit into which branch and then use which
> .config to reproduce?

allmodconfig 

Merge: 1d1df41c5a33 ff9fc0a31d85

1d1df41c5a33 is linux/master 
ff9fc0a31d85 is
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git master

I see:

vmlinux.o: warning: objtool: mce_start()+0x5e: call to __kasan_check_write() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_gather_info()+0x5f: call to v8086_mode.isra.1() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_read_aux()+0x8a: call to mca_msr_reg() leaves .noinstr.text section
vmlinux.o: warning: objtool: do_machine_check()+0x196: call to mce_no_way_out() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_severity_amd.constprop.1()+0xd1: call to mce_severity_amd_smca.isra.0() leaves .noinstr.text section

Let me try again with a clean check out.

  reply	other threads:[~2022-01-19 18:40 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   ` [kbuild-all] " Chen, Rong A
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 [this message]
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=20220119104017.31e5ecc7@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
    --to=kuba@kernel.org \
    --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.