[PATCH 1/2] x86/crash: Use set_memory_p instead of __set_memory_prot
Coiby Xu
coxu at redhat.com
Tue Jan 6 01:50:58 PST 2026
set_memory_p has been introduced since commit 030ad7af9437 ("x86/mm:
Regularize set_memory_p() parameters and make non-static"). There is no
need to use __set_memory_prot.
Signed-off-by: Coiby Xu <coxu at redhat.com>
---
arch/x86/kernel/machine_kexec_64.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/arch/x86/kernel/machine_kexec_64.c b/arch/x86/kernel/machine_kexec_64.c
index 201137b98fb8..0590d399d4f1 100644
--- a/arch/x86/kernel/machine_kexec_64.c
+++ b/arch/x86/kernel/machine_kexec_64.c
@@ -673,10 +673,7 @@ static void kexec_mark_dm_crypt_keys(bool protect)
if (protect)
set_memory_np((unsigned long)phys_to_virt(start_paddr), nr_pages);
else
- __set_memory_prot(
- (unsigned long)phys_to_virt(start_paddr),
- nr_pages,
- __pgprot(_PAGE_PRESENT | _PAGE_NX | _PAGE_RW));
+ set_memory_p((unsigned long)phys_to_virt(start_paddr), nr_pages);
}
}
base-commit: 7f98ab9da046865d57c102fd3ca9669a29845f67
--
2.52.0
More information about the kexec
mailing list