linux-kernel - Re: [ 36/44] x86, microcode: Sanitize per-cpu microcode reloading interface

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120815182645.GA25870@kroah.com>
Date:	Wed, 15 Aug 2012 11:26:45 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk,
	Borislav Petkov <borislav.petkov@....com>,
	Peter Zijlstra <peterz@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [ 36/44] x86, microcode: Sanitize per-cpu microcode reloading
 interface

On Wed, Aug 15, 2012 at 01:30:46PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 15 Aug 2012, Greg Kroah-Hartman wrote:
> > On Tue, Aug 14, 2012 at 09:26:54PM -0300, Henrique de Moraes Holschuh wrote:
> > > I believe the patch bellow, which was required on 3.2, will also be
> > > necessary.
> > 
> > Will it be necessary to apply this before this patch goes in the series,
> > or after it?
> 
> Applying after fixes a build error.  Applying before might avoid the build
> error altogether (error happens when #undef CONFIG_SMP), AFAIK.

Ok, it doesn't apply directly, but looks easy enough to fix up by hand,
I'll go work on that right now...

greg k-h
--
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/