From: Andi Kleen <ak@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] x86/microcode: Handle negative microcode revisions
Date: Sat, 20 Oct 2018 07:13:58 -0700 [thread overview]
Message-ID: <20181020141358.GB27951@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1810201540460.1651@nanos.tec.linutronix.de>
On Sat, Oct 20, 2018 at 03:42:05PM +0200, Thomas Gleixner wrote:
> Andi,
>
> On Fri, 19 Oct 2018, Andi Kleen wrote:
> > Change the comparison to unsigned. With that the loading works
> > as expected.
> >
>
> I assume that wants a fixes tag and needs to be backported to stable,
> right?
I think the bug was there since the original microcode loader, not
sure I can dig out the right commit id for that (it might be
in linux-historic)
Yes please cc stable for this.
-Andi
prev parent reply other threads:[~2018-10-20 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 0:11 [PATCH v1] x86/microcode: Handle negative microcode revisions Andi Kleen
2018-10-20 8:37 ` Borislav Petkov
2018-10-20 13:42 ` Thomas Gleixner
2018-10-20 14:13 ` Andi Kleen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181020141358.GB27951@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.