linux-kernel - Re: [PATCH] x86, FPU: Fix FPU initialization

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]

Message-ID: <20130416113350.GB10452@gmail.com>
Date:	Tue, 16 Apr 2013 13:33:50 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH] x86, FPU: Fix FPU initialization


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

> On Tue, Apr 16, 2013 at 11:25:28AM +0200, Ingo Molnar wrote:
> > I've got limited extra capacity right now - but if Peter rebases
> > tip:x86/cpu or you send a pullable update of tip:x86/cpu I can stick
> > it into -tip testing and yell if it goes wrong.
> >
> 
> Ok, I'll do that in a second.
> 
> Btw, another heads-up: you know how I'm regularly testing
> Linus+tip/master - well, I started seeing some strange lockups on my
> workstation with -rc7 + tip from two days ago. And the box wouldn't
> resume properly, the last line it would print is:
> 
> "Disabling non-boot CPUs ..."
> 
> and then hang. I've backed-out tip/master and it seems to work so it has
> to be some interaction caused by something in tip. I haven't been able
> to put my finger on it though but I'll watch it and try to trigger it on
> my other boxes.

Would be nice to pin that down ...

You are the first one to report this.

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/