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: <alpine.DEB.2.21.1904052220480.1802@nanos.tec.linutronix.de>
Date:   Fri, 5 Apr 2019 22:23:06 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Baoquan He <bhe@...hat.com>
cc:     linux-kernel@...r.kernel.org, kirill.shutemov@...ux.intel.com,
        mingo@...nel.org, bp@...en8.de, hpa@...or.com, dyoung@...hat.com,
        x86@...nel.org
Subject: Re: [PATCH v3 1/3] x86/boot: Add xloadflags bits for 5-level kernel
 checking

On Tue, 12 Mar 2019, Baoquan He wrote:

> Add two bits XLF_5LEVEL and XLF_5LEVEL_ENABLED for 5-level kernel.
> Bit XLF_5LEVEL indicates if 5-level related code is contained
> in this kernel.
> Bit XLF_5LEVEL_ENABLED indicates if CONFIG_X86_5LEVEL=y is set.
> 
> They are being used in later patch to check if kexec/kdump kernel
> is loaded in right place.

Only XLF_5LEVEL is checked. So what's the second flag for?

Thanks,

	tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ