All of lore.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>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/microcode updates
Date: Thu, 19 Feb 2015 13:33:42 +0100	[thread overview]
Message-ID: <20150219123342.GC7047@gmail.com> (raw)
In-Reply-To: <20150219114641.GF31218@pd.tnic>


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

> Hi guys,
> 
> please pull, thanks.
> 
> ---
> The following changes since commit e36f014edff70fc02b3d3d79cead1d58f289332e:
> 
>   Linux 3.19-rc7 (2015-02-01 20:07:21 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/microcode_fixes_for-3.21
> 
> for you to fetch changes up to 35a9ff4eec7a1725ac4364972fc6c156e4feedd0:
> 
>   x86/microcode/intel: Handle truncated microcode images more robustly (2015-02-19 12:42:23 +0100)
> 
> ----------------------------------------------------------------
> * Two fixes hardening microcode data handling. (Quentin Casasnovas)
> 
> ----------------------------------------------------------------
> Quentin Casasnovas (2):
>       x86/microcode/intel: Guard against stack overflow in the loader
>       x86/microcode/intel: Handle truncated microcode images more robustly
> 
>  arch/x86/kernel/cpu/microcode/intel.c       | 5 +++++
>  arch/x86/kernel/cpu/microcode/intel_early.c | 6 +++++-
>  2 files changed, 10 insertions(+), 1 deletion(-)

Pulled into tip:x86/urgent for v3.20 (because they look 
small and beneficial enough fixes), thanks Boris!

	Ingo

      reply	other threads:[~2015-02-19 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 11:46 [GIT PULL] x86/microcode updates Borislav Petkov
2015-02-19 12:33 ` 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=20150219123342.GC7047@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --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.