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: <44fc1530-eb88-d8c5-7465-e48c91799a98@zytor.com>
Date:   Mon, 3 Sep 2018 23:36:11 -0700
From:   "H. Peter Anvin" <hpa@...or.com>
To:     Baoquan He <bhe@...hat.com>, kirill.shutemov@...ux.intel.com
Cc:     x86@...nel.org, kexec@...ts.infradead.org,
        linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...nel.org
Subject: Re: [PATCH 1/3] x86/boot: Add bit fields into xloadflags for 5-level
 kernel checking

On 09/03/18 23:06, Baoquan He wrote:
>>
>> That makes no sense.  I'm talking about *entering* the kernel; the second
>> kernel should switch to 5-level mode as necessary.
> 
> OK, I didn't get your point. I forget what difficulty was met so that
> Kirill need to take this way. In that way, we will never have chance to
> put kernel above 64TB even from 5-level kernel to jump to 5-level
> kernel.
> 

It sounds like you have no intent of doing that anyway?  Now, that is
something one could use an xloadflag for, as I previously stated: "this kernel
supports being entered in 5-level mode."

	-hpa