linux-kernel - Re: [PATCH v2 2/2] mm/memblock: only mark/clear KHO scratch memory when needed

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: <20251127125539.98b2f148c6225f1cb7c9d045@linux-foundation.org>
Date: Thu, 27 Nov 2025 12:55:39 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Usama Arif <usamaarif642@...il.com>
Cc: rppt@...nel.org, kas@...nel.org, changyuanl@...gle.com, graf@...zon.com,
 leitao@...ian.org, thevlad@...a.com, pratyush@...nel.org,
 dave.hansen@...ux.intel.com, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org, kernel-team@...a.com
Subject: Re: [PATCH v2 2/2] mm/memblock: only mark/clear KHO scratch memory
 when needed

On Thu, 27 Nov 2025 20:33:20 +0000 Usama Arif <usamaarif642@...il.com> wrote:

> The scratch memory for kexec handover is used to bootstrap the
> kexec'ed kernel. It is only needed when CONFIG_KEXEC_HANDOVER
> is enabled and only if it is a KHO boot. Add checks to prevent
> marking a KHO scratch region unless needed.

What effect does this change have?  Lessened memory consumption,
presumably.  Of what magnitude and for what time period?