From: Changyuan Lyu <changyuanl@google.com>
To: changyuanl@google.com
Cc: akpm@linux-foundation.org, anthony.yznaga@oracle.com,
arnd@arndb.de, ashish.kalra@amd.com, benh@kernel.crashing.org,
bp@alien8.de, catalin.marinas@arm.com, corbet@lwn.net,
dave.hansen@linux.intel.com, devicetree@vger.kernel.org,
dwmw2@infradead.org, ebiederm@xmission.com, graf@amazon.com,
hpa@zytor.com, jgowans@amazon.com, kexec@lists.infradead.org,
krzk@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, luto@kernel.org, mark.rutland@arm.com,
mingo@redhat.com, pasha.tatashin@soleen.com,
pbonzini@redhat.com, peterz@infradead.org, ptyadav@amazon.de,
robh@kernel.org, rostedt@goodmis.org, rppt@kernel.org,
saravanak@google.com, skinsburskii@linux.microsoft.com,
tglx@linutronix.de, thomas.lendacky@amd.com, will@kernel.org,
x86@kernel.org
Subject: Re: [PATCH v7 14/18] x86/boot: make sure KASLR does not step over KHO preserved memory
Date: Mon, 5 May 2025 13:07:45 -0700 [thread overview]
Message-ID: <20250505200745.1975264-1-changyuanl@google.com> (raw)
In-Reply-To: <20250501225425.635167-15-changyuanl@google.com>
Hi Andrew,
Based on Dave's feedback above, could you please take the following
fix and squash it with "x86/boot: make sure KASLR does not step over
KHO preserved memory" with the updated commit message in mm-unstable?
Thank you very much!
Best,
Changyuan
---- 8< ----
From 464b5750c55f978b47da242f50ec7dbcbac1948c Mon Sep 17 00:00:00 2001
From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Date: Mon, 5 May 2025 11:29:23 -0700
Subject: [PATCH] fixup! x86/boot: make sure KASLR does not step over KHO
preserved memory
During kexec handover (KHO) memory contains data that should be
preserved and this data would be consumed by kexec'ed kernel.
To make sure that the preserved memory is not overwritten, KHO uses
"scratch regions" to bootstrap kexec'ed kernel. These regions are
guaranteed to not have any memory that KHO would preserve and are used as
the only memory the kernel sees during the early boot.
The scratch regions are passed in the setup_data by the first kernel with
other KHO parameters. If the setup_data contains the KHO parameters, limit
randomization to scratch areas only to make sure preserved memory won't get
overwritten.
Since all the pointers in setup_data are represented by u64, they require
double casting (first to unsigned long and then to the actual pointer type)
to compile on 32-bits. This looks goofy out of context, but it is
unfortunately the way that this is handled across the tree. There are at
least a dozen instances of casting like this.
Signed-off-by: Alexander Graf <graf@amazon.com>
Co-developed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Co-developed-by: Changyuan Lyu <changyuanl@google.com>
Signed-off-by: Changyuan Lyu <changyuanl@google.com>
---
arch/x86/boot/compressed/kaslr.c | 26 ++++++++++++--------------
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr.c b/arch/x86/boot/compressed/kaslr.c
index 25de8c3e17cdb..3b0948ad449f9 100644
--- a/arch/x86/boot/compressed/kaslr.c
+++ b/arch/x86/boot/compressed/kaslr.c
@@ -764,25 +764,26 @@ static void process_e820_entries(unsigned long minimum,
* If KHO is active, only process its scratch areas to ensure we are not
* stepping onto preserved memory.
*/
-#ifdef CONFIG_KEXEC_HANDOVER
static bool process_kho_entries(unsigned long minimum, unsigned long image_size)
{
struct kho_scratch *kho_scratch;
struct setup_data *ptr;
+ struct kho_data *kho;
int i, nr_areas = 0;
- ptr = (struct setup_data *)boot_params_ptr->hdr.setup_data;
+ if (!IS_ENABLED(CONFIG_KEXEC_HANDOVER))
+ return false;
+
+ ptr = (struct setup_data *)(unsigned long)boot_params_ptr->hdr.setup_data;
while (ptr) {
if (ptr->type == SETUP_KEXEC_KHO) {
- struct kho_data *kho = (struct kho_data *)ptr->data;
-
- kho_scratch = (void *)kho->scratch_addr;
+ kho = (struct kho_data *)(unsigned long)ptr->data;
+ kho_scratch = (void *)(unsigned long)kho->scratch_addr;
nr_areas = kho->scratch_size / sizeof(*kho_scratch);
-
break;
}
- ptr = (struct setup_data *)ptr->next;
+ ptr = (struct setup_data *)(unsigned long)ptr->next;
}
if (!nr_areas)
@@ -801,13 +802,6 @@ static bool process_kho_entries(unsigned long minimum, unsigned long image_size)
return true;
}
-#else
-static inline bool process_kho_entries(unsigned long minimum,
- unsigned long image_size)
-{
- return false;
-}
-#endif
static unsigned long find_random_phys_addr(unsigned long minimum,
unsigned long image_size)
@@ -824,6 +818,10 @@ static unsigned long find_random_phys_addr(unsigned long minimum,
return 0;
}
+ /*
+ * During kexec handover only process KHO scratch areas that are known
+ * not to contain any data that must be preserved.
+ */
if (!process_kho_entries(minimum, image_size) &&
!process_efi_entries(minimum, image_size))
process_e820_entries(minimum, image_size);
--
2.49.0.967.g6a0df3ecc3-goog
next prev parent reply other threads:[~2025-05-05 20:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 22:54 [PATCH v7 00/18] kexec: introduce Kexec HandOver (KHO) Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 01/18] memblock: add MEMBLOCK_RSRV_KERN flag Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 02/18] memblock: Add support for scratch memory Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 03/18] memblock: introduce memmap_init_kho_scratch() Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 04/18] kexec: add Kexec HandOver (KHO) generation helpers Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 05/18] kexec: add KHO parsing support Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 06/18] kexec: include asm/early_ioremap.h Changyuan Lyu
2025-05-02 0:35 ` Andrew Morton
2025-05-02 18:37 ` Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 07/18] kexec: enable KHO support for memory preservation Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 08/18] kexec: add KHO support to kexec file loads Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 09/18] kexec: add config option for KHO Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 10/18] arm64: add KHO support Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 11/18] x86/setup: use memblock_reserve_kern for memory used by kernel Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 12/18] x86/kexec: add support for passing kexec handover (KHO) data Changyuan Lyu
2025-05-02 18:39 ` Dave Hansen
2025-05-01 22:54 ` [PATCH v7 13/18] x86/e820: temporarily enable KHO scratch for memory below 1M Changyuan Lyu
2025-05-02 18:39 ` Dave Hansen
2025-05-01 22:54 ` [PATCH v7 14/18] x86/boot: make sure KASLR does not step over KHO preserved memory Changyuan Lyu
2025-05-02 18:48 ` Dave Hansen
2025-05-02 21:16 ` Mike Rapoport
2025-05-02 21:36 ` Dave Hansen
2025-05-05 20:07 ` Changyuan Lyu [this message]
2025-05-01 22:54 ` [PATCH v7 15/18] x86/Kconfig: enable kexec handover for 64 bits Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 16/18] memblock: add KHO support for reserve_mem Changyuan Lyu
2025-05-01 22:54 ` [PATCH v7 17/18] Documentation: add documentation for KHO Changyuan Lyu
2025-05-06 2:31 ` Bagas Sanjaya
2025-05-07 17:38 ` Changyuan Lyu
2025-05-07 23:54 ` Bagas Sanjaya
2025-05-01 22:54 ` [PATCH v7 18/18] Documentation: KHO: Add memblock bindings Changyuan Lyu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250505200745.1975264-1-changyuanl@google.com \
--to=changyuanl@google.com \
--cc=akpm@linux-foundation.org \
--cc=anthony.yznaga@oracle.com \
--cc=arnd@arndb.de \
--cc=ashish.kalra@amd.com \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ebiederm@xmission.com \
--cc=graf@amazon.com \
--cc=hpa@zytor.com \
--cc=jgowans@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=ptyadav@amazon.de \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=saravanak@google.com \
--cc=skinsburskii@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox