Skip to contentSkip to conversation

kexec-introduce-is_kho_boot.patch removed from -mm tree

merged mm-nonmm-stable Andrew Morton 1 participant 1 message Sep 14, 2025

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: kexec: introduce is_kho_boot()
has been removed from the -mm tree. Its filename was
kexec-introduce-is_kho_boot.patch

This patch was dropped because it was merged into the mm-nonmm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Evangelos Petrongonas <[email protected]>
Subject: kexec: introduce is_kho_boot()
Date: Thu, 21 Aug 2025 17:58:59 +0000

Patch series "efi: Fix EFI boot with kexec handover (KHO)", v3.

This patch series fixes a kernel panic that occurs when booting with both EFI and KHO (Kexec HandOver) enabled.

The issue arises because EFI's reserve_regions() clears all memory regions with memblock_remove(0, PHYS_ADDR_MAX) before rebuilding them from EFI data. This destroys KHO scratch regions that were set up early during device tree scanning, causing a panic as the kernel has no valid memory regions for early allocations.

The first patch introduces is_kho_boot() to allow early boot components to reliably detect if the kernel was booted via KHO-enabled kexec. The existing kho_is_enabled() only checks the command line and doesn't verify if an actual KHO FDT was passed.

The second patch modifies EFI's reserve_regions() to selectively remove only non-KHO memory regions when KHO is active, preserving the critical scratch regions while still allowing EFI to rebuild its memory map.

This patch (of 3):

During early initialisation, after a kexec, other components, like EFI need to know if a KHO enabled kexec is performed. The kho_is_enabled function is not enough as in the early stages, it only reflects whether the cmdline has KHO enabled, not if an actual KHO FDT exists.

Extend the KHO API with is_kho_boot() to provide a way for components to check if a KHO enabled kexec is performed.

---

 include/linux/kexec_handover.h |    6 ++++++
 kernel/kexec_handover.c        |   20 ++++++++++++++++++++
 2 files changed, 26 insertions(+)
include/linux/kexec_handover.h renamed from include/linux/kexec_handover.h~kexec-introduce-is_kho_boot +6 -0
@@ -40,6 +40,7 @@ struct kho_serialization;
 
 #ifdef CONFIG_KEXEC_HANDOVER
 bool kho_is_enabled(void);
+bool is_kho_boot(void);
 
 int kho_preserve_folio(struct folio *folio);
 int kho_preserve_phys(phys_addr_t phys, size_t size);
@@ -59,6 +60,11 @@ static inline bool kho_is_enabled(void)
 {
 	return false;
 }
+
+static inline bool is_kho_boot(void)
+{
+	return false;
+}
 
 static inline int kho_preserve_folio(struct folio *folio)
 {
kernel/kexec_handover.c renamed from kernel/kexec_handover.c~kexec-introduce-is_kho_boot +20 -0
@@ -952,6 +952,26 @@ static const void *kho_get_fdt(void)
 }
 
 /**
+ * is_kho_boot - check if current kernel was booted via KHO-enabled
+ * kexec
+ *
+ * This function checks if the current kernel was loaded through a kexec
+ * operation with KHO enabled, by verifying that a valid KHO FDT
+ * was passed.
+ *
+ * Note: This function returns reliable results only after
+ * kho_populate() has been called during early boot. Before that,
+ * it may return false even if KHO data is present.
+ *
+ * Return: true if booted via KHO-enabled kexec, false otherwise
+ */
+bool is_kho_boot(void)
+{
+	return !!kho_get_fdt();
+}
+EXPORT_SYMBOL_GPL(is_kho_boot);
+
+/**
  * kho_retrieve_subtree - retrieve a preserved sub FDT by its name.
  * @name: the name of the sub FDT passed to kho_add_subtree().
  * @phys: if found, the physical address of the sub FDT is stored in @phys.

_

Patches currently in -mm which might be from [email protected] are