[1/2] x86/efi: Fix kernel param add_efi_memmap regression

Message ID 20180102172110.17018-2-ard.biesheuvel@linaro.org
State New
Headers show
  • EFI fixes for v4.15
Related show

Commit Message

Ard Biesheuvel Jan. 2, 2018, 5:21 p.m.
From: Dave Young <dyoung@redhat.com>

'add_efi_memmap' is an early param, but do_add_efi_memmap() has no
chance to run because the code path is before parse_early_param().
I believe it worked when the param was introduced but probably later
some other changes caused the wrong order and nobody noticed it.

Move efi_memblock_x86_reserve_range() after parse_early_param()
to fix it.

Signed-off-by: Dave Young <dyoung@redhat.com>

Cc: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>

Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

 arch/x86/kernel/setup.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)


To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 8af2e8d0c0a1..145810b0edf6 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -906,9 +906,6 @@  void __init setup_arch(char **cmdline_p)
 		set_bit(EFI_BOOT, &efi.flags);
 		set_bit(EFI_64BIT, &efi.flags);
-	if (efi_enabled(EFI_BOOT))
-		efi_memblock_x86_reserve_range();
@@ -962,6 +959,8 @@  void __init setup_arch(char **cmdline_p)
+	if (efi_enabled(EFI_BOOT))
+		efi_memblock_x86_reserve_range();
 	 * Memory used by the kernel cannot be hot-removed because Linux