linux-kernel - Re: [GIT PULL] x86, microcode fixes for 3.2

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

Date:	Mon, 26 Mar 2012 07:52:45 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...64.org>
CC:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Jan Beulich <JBeulich@...e.com>
Subject: Re: [GIT PULL] x86, microcode fixes for 3.2

On 03/26/2012 01:48 AM, Borislav Petkov wrote:
> On Sun, Mar 25, 2012 at 12:27:23PM -0700, H. Peter Anvin wrote:
>> I keep wondering if we couldn't have the early-static trap handlers be
>> aware of exception tables, too; they wouldn't have to worry about
>> modules and so it would be reasonably easy.
> 
> Well, we talked about this recently and then we decided we needed the
> extable-sorting-at-build-time patches before we make those static trap
> handlers aware of extables. What happened to those patches, btw? See
> thread at http://marc.info/?l=linux-kernel&m=132196692827070
> 

Hm... I hope that didn't stall out because of me... the amount of
overload I have been under lately is a bit scary.

I was going to dredge out the perfect hash stuff that I had, but the
sorting stuff could be done without that.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/