linux-kernel - Re: i387/FPU init issues...

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]

Date:	Sat, 3 May 2008 21:54:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Mikael Pettersson <mikpe@...uu.se>, jamal <hadi@...erus.ca>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Arjan van de Ven <arjan@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Jan Beulich <jbeulich@...ell.com>
Subject: Re: i387/FPU init issues...

* H. Peter Anvin <hpa@...or.com> wrote:

>> This might also be caused by a calibration error. We've seen enough 
>> of them already.
>
> No doubt.  However, there is *something* ugly going on.

i think a vital clue can be found in the original report:

|  I am able to reproduce the issue consistently on my laptop using qemu 
|  (which helped speed debugging a bit). I have also narrowed it down to 
|  include/asm-x86/i387.h::__save_init_fpu in (32 bit version) - it dies 
|  somewhere in calling the following line:

so it might just be incorrect Qemu emulation of a PII's NOP instruction?

(which btw. probably proves that Linux is the first OS to make 
intelligent use of those instructions?)

	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/