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: Mon, 31 Jan 2022 13:06:45 +0100 [thread overview]
Message-ID: <YffQ1XJ+9YAVa163@zn.tnic> (raw)
In-Reply-To: <20220119153218.02ee6789@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
On Wed, Jan 19, 2022 at 03:32:18PM -0800, Jakub Kicinski wrote:
> On Thu, 20 Jan 2022 00:17:23 +0100 Borislav Petkov wrote:
> > So, I'd like to reproduce that here and play with it a bit. What iso
> > can I install in a guest here so that I can get pretty close to your
> > environment?
>
> It's CentOS Stream 8. It may have some extra backports done by my $corp
> but I don't think the compiler is backported.
Ok, while trying to boot an externally supplied kernel with qemu -kernel
and with a guest install of centos8, I managed to trigger the issues on
the test box.
I've pushed a branch here for you to test:
https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=rc1%2bmce-noinstr
Lemme know how that goes.
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-31 12:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 8:16 kernel test robot
2021-10-26 8:23 ` Borislav Petkov
2021-10-27 7:26 ` [kbuild-all] " Chen, Rong A
2022-01-19 18:22 ` Jakub Kicinski
2022-01-19 18:34 ` Borislav Petkov
2022-01-19 18:40 ` Jakub Kicinski
2022-01-19 19:15 ` Jakub Kicinski
2022-01-19 20:30 ` Borislav Petkov
2022-01-19 20:37 ` Jakub Kicinski
2022-01-19 21:16 ` Borislav Petkov
2022-01-19 22:57 ` Jakub Kicinski
2022-01-19 23:17 ` Borislav Petkov
2022-01-19 23:32 ` Jakub Kicinski
2022-01-31 12:06 ` Borislav Petkov [this message]
2022-01-31 16:56 ` Jakub Kicinski
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=YffQ1XJ+9YAVa163@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome