From: Borislav Petkov <bp@suse.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable-commits@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Patch "x86/mce: Remove noinstr annotation from mce_setup()" has been added to the 5.15-stable tree
Date: Thu, 13 Jan 2022 16:40:00 +0100 [thread overview]
Message-ID: <YeBH0Pui5SD0Tf3T@zn.tnic> (raw)
In-Reply-To: <YeA31erBrPKu755G@kroah.com>
On Thu, Jan 13, 2022 at 03:31:49PM +0100, Greg KH wrote:
> Any hints on how to get rid of this? More patches in the series this
> one came from?
Unfortunately, a whole series:
https://lore.kernel.org/r/20211208111343.8130-1-bp@alien8.de
and the 0day bot guys recently managed to trigger another warning there,
which means even more fixes, even to generic code.
So what that warning tells you is that you call into instrumentable
context from non-instrumentable one. But that has relevance only when
someone traces the MCE code - and up until now I haven't received a
single sensible use case for why that would make any sense.
So long story short, you can safely ignore it and if someone complains,
ask her/him about the use case first and CC me.
:-)
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2022-01-13 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164207874020173@kroah.com>
[not found] ` <YeAnLb7OkkmTWtf/@zn.tnic>
2022-01-13 14:31 ` Patch "x86/mce: Remove noinstr annotation from mce_setup()" has been added to the 5.15-stable tree Greg KH
2022-01-13 15:40 ` Borislav Petkov [this message]
2022-01-13 17:57 ` Greg KH
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=YeBH0Pui5SD0Tf3T@zn.tnic \
--to=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).