linux-kernel - Re: c88d71508e ("x86/boot/64: Rewrite startup_64() in C"): BUG: kernel reboot-without-warning in early-boot stage, last printk: Booting the 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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 16 Jun 2017 10:16:30 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     kernel test robot <fengguang.wu@...el.com>,
        "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Cc:     "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
        LKP <lkp@...org>, linux-kernel@...r.kernel.org,
        wfg@...ux.intel.com, Thomas Gleixner <tglx@...utronix.de>,
        "H. Peter Anvin" <hpa@...or.com>
Subject: Re: c88d71508e ("x86/boot/64: Rewrite startup_64() in C"): BUG:
 kernel reboot-without-warning in early-boot stage, last printk: Booting the
 kernel.


* kernel test robot <fengguang.wu@...el.com> wrote:

> Greetings,
> 
> 0day kernel testing robot got the below dmesg and the first bad commit is
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> 
> commit c88d71508e36b514413464bd2e01f96f34583a0e
> Author:     Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
> AuthorDate: Tue Jun 6 14:31:26 2017 +0300
> Commit:     Ingo Molnar <mingo@...nel.org>
> CommitDate: Tue Jun 13 08:56:54 2017 +0200
> 
>     x86/boot/64: Rewrite startup_64() in C
>     
>     The patch write most of startup_64 logic in C.
>     
>     This is preparation for 5-level paging enabling.
>     
>     Signed-off-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>

Kirill, should I drop the 5-level paging series for now, or is there a fix in the 
works?

Thanks,

	Ingo