linux-kernel - Re: [PATCH 0/4] x86: FPU detection in C

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

Message-ID: <516586CF.90909@zytor.com>
Date:	Wed, 10 Apr 2013 08:35:43 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>
CC:	Ingo Molnar <mingo@...nel.org>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH 0/4] x86: FPU detection in C

On 04/10/2013 06:32 AM, Borislav Petkov wrote:
> (let's test the reply-to-all settings now :-))
> 
> On Wed, Apr 10, 2013 at 02:25:27PM +0200, Ingo Molnar wrote:
>> In my builds I disable that. So I'd suggest to disable that bit in the
>> .config and retry.
> 
> Yep, did that and was able to reproduce the issue in qemu. At a first
> glance, it looks like we're calling kmalloc too early but I need to
> verify this is actually the case. Stay tuned.
> 

OK, this thread took off in another direction but you're still looking
at this, right?

	-hpa


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