linux-kernel - Re: [PATCH v5 00/16] kexec: introduce Kexec HandOver (KHO)

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: <01864D3D-C935-4AA6-85A9-363B14EA5443@kernel.org>
Date: Tue, 25 Mar 2025 11:03:21 -0400
From: Mike Rapoport <rppt@...nel.org>
To: Pasha Tatashin <pasha.tatashin@...een.com>,
 Changyuan Lyu <changyuanl@...gle.com>
CC: linux-kernel@...r.kernel.org, graf@...zon.com, akpm@...ux-foundation.org,
 luto@...nel.org, anthony.yznaga@...cle.com, arnd@...db.de,
 ashish.kalra@....com, benh@...nel.crashing.org, bp@...en8.de,
 catalin.marinas@....com, dave.hansen@...ux.intel.com, dwmw2@...radead.org,
 ebiederm@...ssion.com, mingo@...hat.com, jgowans@...zon.com, corbet@....net,
 krzk@...nel.org, mark.rutland@....com, pbonzini@...hat.com, hpa@...or.com,
 peterz@...radead.org, ptyadav@...zon.de, robh+dt@...nel.org, robh@...nel.org,
 saravanak@...gle.com, skinsburskii@...ux.microsoft.com, rostedt@...dmis.org,
 tglx@...utronix.de, thomas.lendacky@....com, usama.arif@...edance.com,
 will@...nel.org, devicetree@...r.kernel.org, kexec@...ts.infradead.org,
 linux-arm-kernel@...ts.infradead.org, linux-doc@...r.kernel.org,
 linux-mm@...ck.org, x86@...nel.org
Subject: Re: [PATCH v5 00/16] kexec: introduce Kexec HandOver (KHO)



On March 25, 2025 10:19:53 AM EDT, Pasha Tatashin <pasha.tatashin@...een.com> wrote:
>> To use the code, please boot the kernel with the "kho=on" command line
>> parameter.
>> KHO will automatically create scratch regions. If you want to set the
>> scratch size explicitly you can use "kho_scratch=" command line parameter.
>> For instance, "kho_scratch=16M,512M,256M" will reserve a 16 MiB low
>> memory scratch area, a 512 MiB global scratch region, and 256 MiB
>> per NUMA node scratch regions on boot.
>
>kho_scratch= is confusing. It should be renamed to what this memory
>actually represents, which is memory that cannot be preserved by KHO.
>
>I suggest renaming all references to "scratch" and this parameter to:
>
>kho_nopersistent= or kho_nopreserve=

I'm leaning towards kho_bootstrap

>This way, we can also add checks that early allocations done by the
>kernel in this memory do not get preserved. We can also add checks to
>ensure that scarce low DMA memory does not get preserved across
>reboots, and we avoid adding fragmentation to that region.
>
>Pasha
>

-- 
Sincerely yours,
Mike