[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01fbc03e-bef0-bf07-d035-dac695800996@intel.com>
Date: Tue, 8 Nov 2022 15:32:38 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Ashok Raj <ashok.raj@...el.com>, Borislav Petkov <bp@...en8.de>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML Mailing List <linux-kernel@...r.kernel.org>,
X86-kernel <x86@...nel.org>, Tony Luck <tony.luck@...el.com>,
Arjan van de Ven <arjan.van.de.ven@...el.com>,
Andy Lutomirski <luto@...nel.org>,
Jacon Jun Pan <jacob.jun.pan@...el.com>,
Tom Lendacky <thomas.lendacky@....com>,
Kai Huang <kai.huang@...el.com>,
Andrew Cooper <andrew.cooper3@...rix.com>
Subject: Re: [v2 01/13] x86/microcode/intel: Prevent printing updated
microcode rev multiple times
On 11/8/22 15:06, Ashok Raj wrote:
> Patch3 is a bug fix. I suspect some earlier upstream reports of ucode
> failure after update (early loading) might be related. The symptom is
> similar, but those are too old to followup. I got into a similare situation
> when i tried to update an incompatible uCode from initrd and system hung.
Hi Ashok,
If this really is a bug fix, could you please break it out and send it
separately along with appropriate tags like Fixes and a cc:stable@? We
handle bug fixes differently from new features.
Powered by blists - more mailing lists