linux-kernel - Re: [RFC FIX PATCH] x86/e820: Stop kernel boot when RAM resource reservation fails

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:   Mon, 18 Jul 2022 10:42:13 +0000
From:   Boris Petkov <bp@...en8.de>
To:     Bharata B Rao <bharata@....com>, linux-kernel@...r.kernel.org
CC:     tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
        dave.hansen@...ux.intel.com, nikunj@....com, hpa@...or.com,
        Abraham.Shaju@....com
Subject: Re: [RFC FIX PATCH] x86/e820: Stop kernel boot when RAM resource reservation fails

On July 18, 2022 8:58:15 AM UTC, Bharata B Rao <bharata@....com> wrote:
>Currently it is possible to start a guest with memory that
>is beyond the addressable range of CPU. This can typically
>be done by using QEMU without explicilty specifying the max
>physical addressable bits (via phys-bits or host-phys-bits
>options). In such cases QEMU will start the guest with more
>than 1TB memory but would implicitly limit the phys-bits to 40.

Why does the upstream kernel care about some weird qemu guest configurations? 

-- 
Sent from a small device: formatting sux and brevity is inevitable.