linux-kernel - Re: [PATCH v3 1/2] x86: respect memory size limiting via mem= parameter

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: <A93A19ED-0121-4E88-B24E-1593BEBD3384@oracle.com>
Date:   Thu, 14 Feb 2019 04:00:37 -0700
From:   William Kucharski <william.kucharski@...cle.com>
To:     Juergen Gross <jgross@...e.com>
Cc:     linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
        x86@...nel.org, linux-mm@...ck.org, boris.ostrovsky@...cle.com,
        sstabellini@...nel.org, hpa@...or.com, tglx@...utronix.de,
        mingo@...hat.com, bp@...en8.de
Subject: Re: [PATCH v3 1/2] x86: respect memory size limiting via mem=
 parameter



> On Feb 14, 2019, at 3:42 AM, Juergen Gross <jgross@...e.com> wrote:
> 
> When limiting memory size via kernel parameter "mem=" this should be
> respected even in case of memory made accessible via a PCI card.
> 
> Today this kind of memory won't be made usable in initial memory
> setup as the memory won't be visible in E820 map, but it might be
> added when adding PCI devices due to corresponding ACPI table entries.
> 
> Not respecting "mem=" can be corrected by adding a global max_mem_size
> variable set by parse_memopt() which will result in rejecting adding
> memory areas resulting in a memory size above the allowed limit.
> 
> Signed-off-by: Juergen Gross <jgross@...e.com>
> Acked-by: Ingo Molnar <mingo@...nel.org>

Reviewed-by: William Kucharski <william.kucharski@...cle.com>