linux-kernel - Re: [PATCH] x86/mce: Handle AMD threshold interrupt storms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251121093138.GAaSAxet009yCkqd41@fat_crate.local>
Date: Fri, 21 Nov 2025 10:31:38 +0100
From: Borislav Petkov <bp@...en8.de>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: "Naik, Avadhut" <avadnaik@....com>, stable@...r.kernel.org,
	sashal@...nel.org, linux-kernel@...r.kernel.org,
	Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
	Tony Luck <tony.luck@...el.com>,
	Yazen Ghannam <yazen.ghannam@....com>,
	Qiuxu Zhuo <qiuxu.zhuo@...el.com>,
	Avadhut Naik <avadhut.naik@....com>
Subject: Re: [PATCH] x86/mce: Handle AMD threshold interrupt storms

On Fri, Nov 21, 2025 at 08:09:21AM +0100, Greg KH wrote:
> > I think it has not yet been merged into mainline's master branch.
> > This commit was recently accepted into the tip (5th November).
> 
> Then there's nothing we can do about this in the stable tree, please

Yeah, it took me a while to understand what the issue is when Avadhut was
explaining it to me offlist:

So the hunk at the beginning of this thread is needed as a fix for stable
because when they inject a lot of errors back-to-back, after the error storm
detection recovers, they cannot log any errors anymore - see the explanation
in the first patch.

So what we'll do here:

@Avadhut, you take that hunk, pls, and create a separate patch with commit
message explaining everything, blablalba, cc:stable, the whole shebang.

That patch goes upstream and to stable.

The rest of the original

  a5834a5458aa ("x86/mce: Handle AMD threshold interrupt storms")

you then redo ontop of this one and send it too.

I'll zap a5834a5458aa from the lineup for now so that you can split it.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette