linux-kernel - Re: Traceback seen once when running x86 qemu emulation with latest kernel

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

Date:	Sun, 7 Aug 2016 07:14:12 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org
Subject: Re: Traceback seen once when running x86 qemu emulation with latest
 kernel

On Sat, Aug 06, 2016 at 03:41:23PM -0700, Guenter Roeck wrote:
> Hi, I have seen the following traceback once when running the latest mainline in qemu.
> 
> Starting udev
> random: crng init done
> udevd[117]: starting version 182
> Starting Bootlog daemon: bootlogd.
> 
> EXT4-fs (hda): re-mounted. Opts: errors=remount-ro,data=ordered
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at ./arch/x86/include/asm/fpu/internal.h:534 fpu__restore+0x120/0x220

We were debugging this but it has gone nowhere AFAIR:

https://lkml.kernel.org/r/20160211192741.GG5565@pd.tnic
https://lkml.kernel.org/r/87d1rk9str.fsf@yhuang-dev.intel.com

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--