linux-kernel - Re: [PATCH] x86/microcode: Don't duplicate code to update ucode cpu info and cpu info

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: <20180731175035.GB16667@kroah.com>
Date:   Tue, 31 Jul 2018 19:50:35 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     "Sironi, Filippo" <sironi@...zon.de>
Cc:     Borislav Petkov <bp@...en8.de>,
        "prarit@...hat.com" <prarit@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] x86/microcode: Don't duplicate code to update ucode cpu
 info and cpu info

On Tue, Jul 31, 2018 at 04:23:00PM +0000, Sironi, Filippo wrote:
> 
> > On 31. Jul 2018, at 17:41, Greg KH <gregkh@...uxfoundation.org> wrote:
> > 
> > On Tue, Jul 31, 2018 at 05:29:30PM +0200, Filippo Sironi wrote:
> >> ... on late microcode loading when handling a CPU that's already been
> >> updated and a CPU that's yet to be updated.
> >> 
> >> Signed-off-by: Filippo Sironi <sironi@...zon.de>
> >> ---
> >> arch/x86/kernel/cpu/microcode/amd.c   | 15 +++++++++------
> >> arch/x86/kernel/cpu/microcode/intel.c | 10 ++++++----
> >> 2 files changed, 15 insertions(+), 10 deletions(-)
> > 
> > <formletter>
> > 
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree.  Please read:
> >    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> > 
> > </formletter>
> 
> Greg,
> 
> If you're concerned that this isn't a fix, keep in mind that this is going
> to be a prerequisite for https://lore.kernel.org/patchwork/patch/969070/ ,
> which is a bug and was sent to stable.

{sigh}  No, go read the file please...

greg k-h