[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220119104017.31e5ecc7@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Wed, 19 Jan 2022 10:40:17 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Borislav Petkov <bp@...e.de>
Cc: kernel test robot <lkp@...el.com>,
"Paul E. McKenney" <paulmck@...nel.org>, kbuild-all@...ts.01.org,
linux-kernel@...r.kernel.org
Subject: Re: vmlinux.o: warning: objtool: do_machine_check()+0x5fa: call to
memset() leaves .noinstr.text section
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.
Powered by blists - more mailing lists