linux-kernel - Re: [GIT PULL] x86, microcode, AMD: Fixes for next merge window

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] [day] [month] [year] [list]

Message-ID: <20111215071307.GE14237@elte.hu>
Date:	Thu, 15 Dec 2011 08:13:07 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Borislav Petkov <bp@...64.org>
Cc:	Andreas Herrmann <andreas.herrmann3@....com>, x86 <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] x86, microcode, AMD: Fixes for next merge window


* Borislav Petkov <bp@...64.org> wrote:

> Hi Ingo,
> 
> as promised, please pull from the branch below to receive the following
> fixes, they could be queued for the next merge window and simmer a while
> in linux-next until then.
> 
> Thanks.
> 
> The following changes since commit dc47ce90c3a822cd7c9e9339fe4d5f61dcb26b50:
> 
>   Linux 3.2-rc5 (2011-12-09 15:09:32 -0800)
> 
> are available in the git repository at:
>   git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git ucode-verify-size
> 
> Borislav Petkov (5):
>       x86, microcode, AMD: Add a vendor-specific exit function
>       x86, microcode, AMD: Add a reusable buffer
>       x86, microcode, AMD: Simplify ucode verification
>       x86, microcode, AMD: Exit early on success
>       x86, microcode, AMD: Update copyrights
> 
>  arch/x86/include/asm/microcode.h |    2 +
>  arch/x86/kernel/microcode_amd.c  |  209 +++++++++++++++++++++-----------------
>  arch/x86/kernel/microcode_core.c |    5 +
>  3 files changed, 121 insertions(+), 95 deletions(-)

Pulled, thanks a lot Boris!

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/