Skip to contentSkip to conversation

Patch "efi: Process the MEMATTR table only if EFI_MEMMAP is enabled" has been added to the 4.11-stable tree

PATCH [email protected] 1 participant 1 message Jul 18, 2017

Subsystems (2)
lore
Share & tools
lore

[email protected]

author maintainer Applied
#0 lore raw

This is a note to let you know that I've just added the patch titled

efi: Process the MEMATTR table only if EFI_MEMMAP is enabled

to the 4.11-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
efi-process-the-memattr-table-only-if-efi_memmap-is-enabled.patch
and it can be found in the queue-4.11 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

Quoted 1 line

From 457ea3f7e97881f937136ce0ba1f29f82b9abdb0 Mon Sep 17 00:00:00 2001

From: Daniel Kiper <[email protected]>
Date: Thu, 22 Jun 2017 12:51:36 +0200
Subject: efi: Process the MEMATTR table only if EFI_MEMMAP is enabled

From: Daniel Kiper <[email protected]>

commit 457ea3f7e97881f937136ce0ba1f29f82b9abdb0 upstream.

Otherwise e.g. Xen dom0 on x86_64 EFI platforms crashes.

In theory we can check EFI_PARAVIRT too, however, EFI_MEMMAP looks more targeted and covers more cases.

---
 drivers/firmware/efi/efi.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/firmware/efi/efi.c +2 -1
@@ -528,7 +528,8 @@ int __init efi_config_parse_tables(void
 		}
 	}
 
-	efi_memattr_init();
+	if (efi_enabled(EFI_MEMMAP))
+		efi_memattr_init();
 
 	/* Parse the EFI Properties table if it exists */
 	if (efi.properties_table != EFI_INVALID_TABLE_ADDR) {

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

queue-4.11/efi-process-the-memattr-table-only-if-efi_memmap-is-enabled.patch