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: <cd62e6b9-aec4-b8a5-be71-7edc10734955@intel.com>
Date:   Wed, 29 Aug 2018 13:28:16 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Michal Hocko <mhocko@...e.com>,
        Andi Kleen <ak@...ux.intel.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>, x86@...nel.org,
        Joerg Roedel <jroedel@...e.de>, Pavel Machek <pavel@....cz>
Subject: Re: efi boot failures due to PTI with 32 bit builds and Intel CPUs

On 08/29/2018 01:16 PM, Guenter Roeck wrote:
> 
> I see boot failures on mainline when trying to boot x86 images with an efi
> bios on Intel CPUs in qemu. Behavior is quite unusual: qemu dies silently
> after the kernel displays "Run /sbin/init as init process". With debugging
> enabled, qemu reports a CR3 update followed by a triple fault.

My first thought would be that the EFI pgd is broken somehow.

Is 0e39b000 in your kernel binary, or was it dynamically allocated?

What was CR2 when things went bad?  Could you just share a full register
dump?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ