linux-kernel - [PATCH v2 0/2] mm: 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-next>] [day] [month] [year] [list]

Message-ID: <20251127203724.3177621-1-usamaarif642@gmail.com>
Date: Thu, 27 Nov 2025 20:33:18 +0000
From: Usama Arif <usamaarif642@...il.com>
To: rppt@...nel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Cc: 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,
	Usama Arif <usamaarif642@...il.com>
Subject: [PATCH v2 0/2] mm: only mark/clear KHO scratch memory when needed

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.

CONFIG_MEMBLOCK_KHO_SCRATCH is also removed as its only selected
by KEXEC_HANDOVER.

v1 -> v2:
- Remove CONFIG_MEMBLOCK_KHO_SCRATCH (Kiryl Shutsemau)
- Move memblock_mark/clear_kho_scratch under alread existing
  CONFIG_KEXEC_HANDOVER in memblock.c.

Usama Arif (2):
  mm/memblock: remove CONFIG_MEMBLOCK_KHO_SCRATCH option
  mm/memblock: only mark/clear KHO scratch memory when needed

 include/linux/memblock.h |  2 +-
 kernel/Kconfig.kexec     |  1 -
 mm/Kconfig               |  4 ---
 mm/memblock.c            | 78 +++++++++++++++++++++++-----------------
 4 files changed, 47 insertions(+), 38 deletions(-)

-- 
2.47.3