linux-kernel - Re: [PATCH 1/3] memblock: define functions to set the usable memory range

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: <20220114002252.GA22602@dev-dsk-fllinden-2c-d7720709.us-west-2.amazon.com>
Date:   Fri, 14 Jan 2022 00:22:52 +0000
From:   Frank van der Linden <fllinden@...zon.com>
To:     Mike Rapoport <rppt@...nel.org>
CC:     <linux-arm-kernel@...ts.infradead.org>, <robh+dt@...nel.org>,
        <frowand.list@...il.com>, <ardb@...nel.org>, <linux-mm@...ck.org>,
        <devicetree@...r.kernel.org>, <linux-efi@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <kexec@...ts.infradead.org>,
        <catalin.marinas@....com>, <will@...nel.org>,
        <geert+renesas@...der.be>
Subject: Re: [PATCH 1/3] memblock: define functions to set the usable memory
 range

On Fri, Jan 14, 2022 at 12:10:46AM +0000, Frank van der Linden wrote:
> Thanks for discussing this further! I tried the above change, although
> I wrapped it in an if (cap_mem_size != 0), so that a normal kernel
> doesn't get its entire memory marked as reserved.

Just to clarify: I had to do that because the code is slightly different
on 5.15, where I tried it. It wasn't a bug in the proposed patch.

Anyway, will try 5.17-rc tomorrow, I'll let you know, thanks again.

- Frank