From: Borislav Petkov <bp@suse.de>
To: Jakub Kicinski <kuba@kernel.org>
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 22:16:16 +0100 [thread overview]
Message-ID: <Yeh/oEYGyg2+XYSJ@zn.tnic> (raw)
In-Reply-To: <20220119123714.22b54d4c@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
On Wed, Jan 19, 2022 at 12:37:14PM -0800, Jakub Kicinski wrote:
> gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-3)
I have
$ gcc-8 --version
gcc-8 (SUSE Linux) 8.2.1 20180831 [gcc-8-branch revision 264010]
but I can't trigger anything with it either.
So I had a report about a randconfig from the 0day robot guys which
doesn't look like allmodconfig but which triggered some of the issues
you're seeing and I have fixes for that one which we wanna queue after
-rc1.
You could try them to see if they fix your warnings too. First take the
2 here:
https://lore.kernel.org/r/20220113155357.4706-1-bp@alien8.de
and then this one ontop:
https://lore.kernel.org/r/YeWsopFagTZ4W8WA@zn.tnic
Thx.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@suse.de>
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 22:16:16 +0100 [thread overview]
Message-ID: <Yeh/oEYGyg2+XYSJ@zn.tnic> (raw)
In-Reply-To: <20220119123714.22b54d4c@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Wed, Jan 19, 2022 at 12:37:14PM -0800, Jakub Kicinski wrote:
> gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-3)
I have
$ gcc-8 --version
gcc-8 (SUSE Linux) 8.2.1 20180831 [gcc-8-branch revision 264010]
but I can't trigger anything with it either.
So I had a report about a randconfig from the 0day robot guys which
doesn't look like allmodconfig but which triggered some of the issues
you're seeing and I have fixes for that one which we wanna queue after
-rc1.
You could try them to see if they fix your warnings too. First take the
2 here:
https://lore.kernel.org/r/20220113155357.4706-1-bp(a)alien8.de
and then this one ontop:
https://lore.kernel.org/r/YeWsopFagTZ4W8WA(a)zn.tnic
Thx.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2022-01-19 21:16 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
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 [this message]
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=Yeh/oEYGyg2+XYSJ@zn.tnic \
--to=bp@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.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.