On Thu, Jan 13, 2022 at 04:40:00PM +0100, Borislav Petkov wrote:
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.
:-)
Ok, will just ignore it, 5.16.y should only be alive for a few months (4?) so it's not that big of a deal, I was just trying to ensure 0-warning builds were happening as it's easier to notice when I mess something up with the stable releases.
I'll go drop this commit now, thanks.
greg k-h