linux-kernel - Re: [tip: x86/urgent] x86/cpu/amd: Fix workaround for erratum 1054

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2025041819-harsh-outreach-dd6d@gregkh>
Date: Fri, 18 Apr 2025 14:47:39 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Ingo Molnar <mingo@...nel.org>, stable <stable@...r.kernel.org>,
	linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org,
	Sandipan Das <sandipan.das@....com>, x86@...nel.org
Subject: Re: [tip: x86/urgent] x86/cpu/amd: Fix workaround for erratum 1054

On Fri, Apr 18, 2025 at 02:37:13PM +0200, Borislav Petkov wrote:
> On Fri, Apr 18, 2025 at 02:11:44PM +0200, Ingo Molnar wrote:
> > No, it doesn't really 'need' a stable tag, it has a Fixes tag already, 
> > which gets processed by the -stable team.

NOOOOOO!!!!

> Last time I asked Greg, he said they scan for those tags but it doesn't hurt
> to Cc stable as it helps.
> 
> Greg?

Fixes: is a "best effort if we get around to it because a maintainer
forgot to put an actual cc: stable tag on it".

As the documentation has stated, since the start of the stable kernel
tree work, use a cc: stable tag if you want it to go to a stable tree.
Fixes came years later and we are forced to dig through them
occasionally because people forget.  But you do NOT get a FAILED email
if the commit does not apply to a stable tree, and sometimes we just
ignore them entirely if we are busy with other stuff.

So please ALWAYS use cc: stable@ on patches you know you want to be
applied to stable trees.  Use the Fixes: tag to tell us how far back to
backport them.  That's it.  Use both.

thanks,

greg k-h