linux-kernel - Re: [PATCH 1/3] x86/boot: Add bit fields into xloadflags for 5-level kernel checking

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: <6ea94875-ae07-6220-eb3e-d3f830cdac03@zytor.com>
Date:   Mon, 3 Sep 2018 19:41:29 -0700
From:   "H. Peter Anvin" <hpa@...or.com>
To:     Baoquan He <bhe@...hat.com>, tglx@...utronix.de, mingo@...nel.org,
        kirill.shutemov@...ux.intel.com
Cc:     x86@...nel.org, linux-kernel@...r.kernel.org,
        kexec@...ts.infradead.org
Subject: Re: [PATCH 1/3] x86/boot: Add bit fields into xloadflags for 5-level
 kernel checking

I don't understand why there is any reason not to always enter the target
kernel in 4-level mode.  There certainly is no point whatsoever in having two
xloadflags: the only thing that could possibly matter is whether or not the
kernel in question *can* be entered in 5-level mode should that ever be necessary.

	-hpa