public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>,
	Quentin Casasnovas <quentin.casasnovas@oracle.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] microcode loader updates
Date: Tue, 3 Mar 2015 13:55:47 +0100	[thread overview]
Message-ID: <20150303125547.GA1951@gmail.com> (raw)
In-Reply-To: <20150302123441.GB17521@pd.tnic>


* Borislav Petkov <bp@alien8.de> wrote:

> Hi guys,
> 
> here's the first pile of microcode loader cleanups for 4.1.
> 
> Please pull,
> thanks.
> 
> ---
> The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
> 
>   Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/intel_microcode_cleanup_p1
> 
> for you to fetch changes up to 94a7cbf93996711a32e286488b8523740d6a19f0:
> 
>   x86/microcode/intel: Fix printing of microcode blobs in show_saved_mc() (2015-03-02 10:07:36 +0100)
> 
> ----------------------------------------------------------------
> The first part of the scrubbing of the intel early microcode loader.
> There's more work to come but let's unload this pile first.
> 
> ----------------------------------------------------------------
> Borislav Petkov (13):
>       x86/microcode/intel: Check if microcode was found before applying
>       x86/microcode/intel: Do the mc_saved_src NULL check first
>       x86/microcode/intel: Get rid of last arg to load_ucode_intel_bsp()
>       x86/microcode/intel: Simplify load_ucode_intel_bsp()
>       x86/microcode/intel: Make _save_mc() return the updated saved count
>       x86/microcode/intel: Sanitize _save_mc()
>       x86/microcode/intel: Rename update_match_revision()
>       x86/microcode: Consolidate family,model, ... code
>       x86/microcode/intel: Simplify generic_load_microcode_early()
>       x86/microcode/intel: Move mc arg last in get_matching_{microcode|sig}
>       x86/microcode/intel: Sanitize microcode_pointer()
>       x86/microcode/intel: Check scan_microcode()'s retval
>       x86/microcode/intel: Fix printing of microcode blobs in show_saved_mc()
> 
> Quentin Casasnovas (1):
>       x86/microcode/intel: Fix out of bounds memory access to the extended header
> 
>  arch/x86/include/asm/microcode.h            |  73 ++++++
>  arch/x86/include/asm/microcode_intel.h      |  13 +-
>  arch/x86/kernel/cpu/microcode/core_early.c  |  75 +-----
>  arch/x86/kernel/cpu/microcode/intel.c       |   4 +-
>  arch/x86/kernel/cpu/microcode/intel_early.c | 344 +++++++++++++---------------
>  arch/x86/kernel/cpu/microcode/intel_lib.c   |  22 +-
>  6 files changed, 259 insertions(+), 272 deletions(-)

Pulled the updated version into tip:x86/microcode, thanks Boris!

	Ingo

      parent reply	other threads:[~2015-03-03 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 12:34 [GIT PULL] microcode loader updates Borislav Petkov
2015-03-02 13:03 ` Quentin Casasnovas
2015-03-02 13:29   ` Borislav Petkov
2015-03-02 13:42     ` Quentin Casasnovas
2015-03-02 15:04       ` Borislav Petkov
2015-03-02 15:29         ` Quentin Casasnovas
2015-03-02 17:48 ` Borislav Petkov
2015-03-03 12:55 ` Ingo Molnar [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=20150303125547.GA1951@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quentin.casasnovas@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox