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: <20220124210538.GA15943@dev-dsk-fllinden-2c-d7720709.us-west-2.amazon.com>
Date:   Mon, 24 Jan 2022 21:05:38 +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

Meanwhile, it seems that this issue was already addressed in:

https://lore.kernel.org/all/20211215021348.8766-1-kernelfans@gmail.com/

..which has now been pulled in, and sent to stable@ for 5.15. I
somehow missed that message, and sent my change in a few weeks
later.

The fix to just reserve the ranges does seem a bit cleaner overall,
but this will do fine.

Thanks!

- Frank

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ