linux-kernel - Re: [GIT PULL, v2] x86/microcode tree changes for v3.19

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: <20141211122558.GA18538@gmail.com>
Date:	Thu, 11 Dec 2014 13:25:58 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL, v2] x86/microcode tree changes for v3.19


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

> On Thu, Dec 11, 2014 at 07:25:08AM +0100, Ingo Molnar wrote:
> > > Hmm. There's a conflict with commit 02ecc41abcea ("x86, 
> > > microcode: Limit the microcode reloading to 64-bit for now"), 
> > 
> > Sorry, should have mentioned that explicitly, but forgot about 
> > it.
> > 
> > > but I'm going to assume that the issue is fixed now, and that 
> > > commit fbae4ba8c4a3 ("x86, microcode: Reload microcode on 
> > > resume") that causes the conflict also handles the 32-bit case 
> > > correctly. So my merge is going to just remove the X86_64 test, 
> > > effectively undoing that first commit, ratehr than keep it 
> > > around.
> 
> Yes, this is the intended outcome.

Ok, great!

Thanks,

	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/