All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 4.4] x86/microcode/intel: Fix BDW late-loading revision check
Date: Wed, 24 Jan 2018 10:20:28 +0100	[thread overview]
Message-ID: <20180124092028.GA19411@kroah.com> (raw)
In-Reply-To: <20180124023119.kaendz4jiuejowxr@xylophone.i.decadent.org.uk>

On Wed, Jan 24, 2018 at 02:31:19AM +0000, Ben Hutchings wrote:
> The backport of commit b94b73733171 ("x86/microcode/intel: Extend BDW
> late-loading with a revision check") to 4.4-stable deleted a "return true"
> statement.  This bug is not present upstream or other stable branches.
> 
> Signed-off-by: Ben Hutchings <ben.hutchings@codethink.co.uk>
> ---
>  arch/x86/kernel/cpu/microcode/intel.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/x86/kernel/cpu/microcode/intel.c b/arch/x86/kernel/cpu/microcode/intel.c
> index b428a8174be1..ee011bd7934d 100644
> --- a/arch/x86/kernel/cpu/microcode/intel.c
> +++ b/arch/x86/kernel/cpu/microcode/intel.c
> @@ -1005,6 +1005,7 @@ static bool is_blacklisted(unsigned int cpu)
>  	    c->microcode < 0x0b000021) {
>  		pr_err_once("Erratum BDF90: late loading with revision < 0x0b000021 (0x%x) disabled.\n", c->microcode);
>  		pr_err_once("Please consider either early loading through initrd/built-in or a potential BIOS update.\n");
> +		return true;
>  	}

That is really odd.  Thanks for catching this, now queued up.

greg k-h

  reply	other threads:[~2018-01-24  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24  2:31 [PATCH 4.4] x86/microcode/intel: Fix BDW late-loading revision check Ben Hutchings
2018-01-24  9:20 ` Greg Kroah-Hartman [this message]
2018-01-24  9:25 ` Patch "x86/microcode/intel: Fix BDW late-loading revision check" has been added to the 4.4-stable tree gregkh

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=20180124092028.GA19411@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=stable@vger.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.