linux-kernel - Re: PANIC: double fault, error_code: 0x0 in 4.0.0-rc3-2, kvm related?

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:	Thu, 19 Mar 2015 13:48:56 +0100
From:	Denys Vlasenko <vda.linux@...glemail.com>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	Denys Vlasenko <dvlasenk@...hat.com>,
	Andy Lutomirski <luto@...capital.net>,
	Jiri Kosina <jkosina@...e.cz>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Stefan Seyfried <stefan.seyfried@...glemail.com>,
	X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: PANIC: double fault, error_code: 0x0 in 4.0.0-rc3-2, kvm related?

Having no more ideas at the moment, here is a tarball of 13 patches
of commits touching entry_64.S up to 4.0.0-rc1.

x0001.patch is the latest, x0015.patch is the oldest.

Patches 0003 and 0008 are not there since 0003 is empty merge patch
and 0008 does some PCI fixup.

If this breakage is recent, it ought to be one of these.
Most of them do some non-trivial surgery.

Even though I did not spot anything suspicious in them,
entry.S is notorious for subtle breakage.

Try reverting them in sequence starting from x0001.patch
and see reverting which one makes crash disappear.

Download attachment "revert_me_13.tar.gz" of type "application/x-gzip" (20340 bytes)