efi/memattr: Fix memory corruption and warning issues
Subsystems (4)
cover efi/memattr: Fix memory corruption and warning issues
Since the patch with the warning in [1] was merged, a very significant number of kexec boots are producing the warning in our (Meta) fleet.
I believe there are 2 problems, the warning itself might not be
triggered on the right condition, and memory attributes
table is getting corrupted.
An example of the warning when its not triggered correctly and
is fixed by patch 1:
efi: memattr: [Firmware Bug]: Corrupted EFI Memory Attributes Table detected! (version == 2, desc_size == 48, num_entries == 48) An example of the warning when memory attributes table
is getting corrupted and might possibly be fixed by patch 2:
efi: memattr: [Firmware Bug]: Corrupted EFI Memory Attributes Table detected! (version == 1, desc_size == 2072184435, num_entries == 3248688968) Its clear that the desc size and num_entries are wrong.
The logic behind patch 1 is explained in its commit message.
The memory corruption is looking very similar to the problem that was fixed by 77d48d39e99170 ("efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption"), but this time with memattr table, where it might not be preserved during kexec. I have
not been able to reproduce this in the test machine I have over the past couple of days (hence marked as RFC) , but its happening often in our prod.
When this area is not reserved, it comes up as usable in /sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region where efi_mem_attr_table is and overwrite it and relocate_kernel.
Having a fix in firmware can be difficult to get through.
The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service
call option [3], [4], I tried to use install_configuration_table as
a substitute, but its not valid and corrupts the MemoryAttributesTable.
The prints I got from the below code in coverletter were:
EFI stub: ERROR: KKK tbl 5f19e018 tbl_>version=1, tbl->num_entries 48 tbl->desc_size 48 EFI stub: ERROR: KKK2 tbl 67184018 tbl_>version=2048, tbl->num_entries 0 tbl->desc_size 0 which shows the table got corrupted. This can bee seen in the kernel boot as well after (with the version showing up as 2048).
As a last option for a fix, the patch marks that region as reserved in e820_table_firmware if it is currently E820_TYPE_RAM so that kexec doesn't use it for kernel segments.
[1] https://lore.kernel.org/all/[email protected]/
[2] https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Misc/MemoryAttributesTable.c#L100
[3] https://github.com/tianocore/edk2/blob/42a141800c0c26a09d2344e84a89ce4097a263ae/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c#L41
[4] https://elixir.bootlin.com/linux/v6.12.6/source/drivers/firmware/efi/libstub/efistub.h#L327
drivers/firmware/efi/libstub/efistub.h +1 -0
@@ -1143,6 +1143,7 @@ efi_enable_reset_attack_mitigation(void) { }#endif void efi_retrieve_eventlog (void ); +void efi_mem_attr_init (void );struct screen_info *alloc_screen_info (void );struct screen_info *__alloc_screen_info (void );
drivers/firmware/efi/libstub/mem.c +32 -0
@@ -128,3 +128,35 @@ void efi_free(unsigned long size, unsigned long addr) nr_pages =round_up (size,EFI_ALLOC_ALIGN ) /EFI_PAGE_SIZE ;efi_bs_call (free_pages, addr, nr_pages); } + +void efi_mem_attr_init (void ) +{ +efi_guid_t linux_mem_attr_guid =EFI_MEMORY_ATTRIBUTES_TABLE_GUID ; +efi_memory_attributes_table_t *tbl =NULL ; +efi_status_t status; +unsigned long size; + + tbl =get_efi_config_table (linux_mem_attr_guid); +efi_err ("KKK tbl %lx tbl_>version=%d, tbl->num_entries %d tbl->desc_size %d\n" , tbl, tbl->version, tbl->num_entries, tbl->desc_size); + + size = tbl->num_entries * tbl->desc_size; + status =efi_bs_call (allocate_pool,EFI_ACPI_RECLAIM_MEMORY , +sizeof (*tbl) + size, (void **)&tbl); + +if (status !=EFI_SUCCESS ) { +efi_err ("Unable to allocate memory for event log\n" ); +return ; + } + + status =efi_bs_call (install_configuration_table, + &linux_mem_attr_guid, tbl); + +if (status !=EFI_SUCCESS ) +efi_err ("Unable to install configuration table to update memory type\n" ); +efi_bs_call (free_pool, tbl); + +/* verify if its the same table */ + tbl =get_efi_config_table (linux_mem_attr_guid); +efi_err ("KKK2 tbl %lx tbl_>version=%d, tbl->num_entries %d tbl->desc_size %d\n" , tbl, tbl->version, tbl->num_entries, tbl->desc_size); + +}
drivers/firmware/efi/libstub/x86-stub.c +2 -0
@@ -1036,6 +1036,8 @@ void __noreturn efi_stub_entry(efi_handle_t handle,efi_retrieve_eventlog (); +efi_mem_attr_init (); +setup_graphics (boot_params);setup_efi_pci (boot_params);
Usama Arif (2):
efi/memattr: Use desc_size instead of total size to check for
corruption
efi/memattr: add efi_mem_attr_table as a reserved region in
820_table_firmware
arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/e820.c | 6 ++++++ arch/x86/platform/efi/efi.c | 9 +++++++++ drivers/firmware/efi/memattr.c | 17 +++++++---------- include/linux/efi.h | 7 +++++++ 5 files changed, 31 insertions(+), 10 deletions(-)
Signature · 1 line
2.43.5
RFC 1/2 efi/memattr: Use desc_size instead of total size to check for corruption
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.
This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size = 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.
In late boot __efi_enter_virtual_mode calls 2 functions that updates efi.memmap.nr_map:
- efi_map_regions which reduces the count of map entries
(for e.g. if should_map_region returns false) and which is reflected in efi.memmap by __efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
- efi_free_boot_services which also reduces the number of memory regions available (for e.g. if md->type or md->attribute is not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size = 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due to efi_map_regions and efi_free_boot_services.
A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)
drivers/firmware/efi/memattr.c +6 -10
@@ -40,21 +40,17 @@ int __init efi_memattr_init(void) goto unmap; } -/* -* Sanity check: the Memory Attributes Table contains up to 3 entries -* for each entry of type EfiRuntimeServicesCode in the EFI memory map. -* So if the size of the table exceeds 3x the size of the entire EFI -* memory map, there is clearly something wrong, and the table should -* just be ignored altogether. +* Sanity check: the Memory Attributes Table desc_size and +* efi.memmap.desc_size should match. */ - size = tbl->num_entries * tbl->desc_size; -if (size >3 * efi.memmap.nr_map * efi.memmap.desc_size) { -pr_warn (FW_BUG "Corrupted EFI Memory Attributes Table detected! (version == %u, desc_size == %u, num_entries == %u)\n" , - tbl->version, tbl->desc_size, tbl->num_entries); +if (efi.memmap.desc_size != tbl->desc_size) { +pr_warn (FW_BUG "Corrupted EFI Memory Attributes Table detected! (version == %u, table desc_size == %u, efi.memmap.desc_size == %lu, table num_entries == %u)\n" , + tbl->version, tbl->desc_size, efi.memmap.desc_size, tbl->num_entries); goto unmap; } + size = tbl->num_entries * tbl->desc_size; tbl_size =sizeof (*tbl) + size;memblock_reserve (efi_mem_attr_table, tbl_size);set_bit (EFI_MEM_ATTR , &efi.flags);
Signature · 1 line
2.43.5
Ard Biesheuvel
maintainerRe: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 36 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
Quoted 9 lines
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
The main reason is that the EFI memory map and the EFI memory attributes table are supposed to be a matched pair, where each RTcode entry in the former is broken down into multiple code and data segments in the latter. The amount of mangling that the x86 arch code does of the EFI memory map makes it intractable to ensure that they remain in sync, and so it is better not to bother.
Quoted 35 lines
drivers/firmware/efi/memattr.c +6
-11@@ -40,21 +40,17 @@ int __init efi_memattr_init(void) goto unmap; } -/* -* Sanity check: the Memory Attributes Table contains up to 3 entries -* for each entry of type EfiRuntimeServicesCode in the EFI memory map. -* So if the size of the table exceeds 3x the size of the entire EFI -* memory map, there is clearly something wrong, and the table should -* just be ignored altogether. +* Sanity check: the Memory Attributes Table desc_size and +* efi.memmap.desc_size should match. */ - size = tbl->num_entries * tbl->desc_size; -if (size >3 * efi.memmap.nr_map * efi.memmap.desc_size) { -pr_warn (FW_BUG "Corrupted EFI Memory Attributes Table detected! (version == %u, desc_size == %u, num_entries == %u)\n" , - tbl->version, tbl->desc_size, tbl->num_entries); +if (efi.memmap.desc_size != tbl->desc_size) { +pr_warn (FW_BUG "Corrupted EFI Memory Attributes Table detected! (version == %u, table desc_size == %u, efi.memmap.desc_size == %lu, table num_entries == %u)\n" , + tbl->version, tbl->desc_size, efi.memmap.desc_size, tbl->num_entries); goto unmap; } + size = tbl->num_entries * tbl->desc_size; tbl_size =sizeof (*tbl) + size;memblock_reserve (efi_mem_attr_table, tbl_size);set_bit (EFI_MEM_ATTR , &efi.flags); --2.43.5
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 47 lines · Ard Biesheuvel
Quoted 36 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
Quoted 9 lines
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use e820_table_firmware? Also a very basic question, what do you mean by run with the firmware RWX?
Sorry for the very basic questions above!
Quoted 44 lines
The main reason is that the EFI memory map and the EFI memory attributes table are supposed to be a matched pair, where each RTcode entry in the former is broken down into multiple code and data segments in the latter. The amount of mangling that the x86 arch code does of the EFI memory map makes it intractable to ensure that they remain in sync, and so it is better not to bother.
Quoted 35 lines
drivers/firmware/efi/memattr.c +6
-11@@ -40,21 +40,17 @@ int __init efi_memattr_init(void) goto unmap; } -/* -* Sanity check: the Memory Attributes Table contains up to 3 entries -* for each entry of type EfiRuntimeServicesCode in the EFI memory map. -* So if the size of the table exceeds 3x the size of the entire EFI -* memory map, there is clearly something wrong, and the table should -* just be ignored altogether. +* Sanity check: the Memory Attributes Table desc_size and +* efi.memmap.desc_size should match. */ - size = tbl->num_entries * tbl->desc_size; -if (size >3 * efi.memmap.nr_map * efi.memmap.desc_size) { -pr_warn (FW_BUG "Corrupted EFI Memory Attributes Table detected! (version == %u, desc_size == %u, num_entries == %u)\n" , - tbl->version, tbl->desc_size, tbl->num_entries); +if (efi.memmap.desc_size != tbl->desc_size) { +pr_warn (FW_BUG "Corrupted EFI Memory Attributes Table detected! (version == %u, table desc_size == %u, efi.memmap.desc_size == %lu, table num_entries == %u)\n" , + tbl->version, tbl->desc_size, efi.memmap.desc_size, tbl->num_entries); goto unmap; } + size = tbl->num_entries * tbl->desc_size; tbl_size =sizeof (*tbl) + size;memblock_reserve (efi_mem_attr_table, tbl_size);set_bit (EFI_MEM_ATTR , &efi.flags); --2.43.5
Ard Biesheuvel
maintainerRe: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 51 lines · Usama Arif
Quoted 47 lines · Ard Biesheuvel
Quoted 45 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)
Quoted 6 lines
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use
e820_table_firmware?
No, I mean kexec ignores the memory attributes table.
Quoted 2 lines
Also a very basic question, what do you mean by run with the firmware RWX?
The memory attributes table is an overlay for the EFI memory map that describes which runtime code regions may be mapped with restricted permissions. Without this table, everything will be mapped writable as well as executable, but only in the EFI page tables, which are only active when an EFI call is in progress.
Quoted 2 lines
Sorry for the very basic questions above!
No worries.
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 61 lines · Ard Biesheuvel
Quoted 51 lines · Usama Arif
Quoted 47 lines · Ard Biesheuvel
Quoted 45 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)Quoted 6 lines
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use
e820_table_firmware?No, I mean kexec ignores the memory attributes table.
Quoted 9 lines
Quoted 2 lines
Also a very basic question, what do you mean by run with the firmware RWX?
The memory attributes table is an overlay for the EFI memory map that describes which runtime code regions may be mapped with restricted permissions. Without this table, everything will be mapped writable as well as executable, but only in the EFI page tables, which are only active when an EFI call is in progress.
Thanks for explaining!
So basically get rid of memattr.c :)
Do you mean get rid of it only for kexec, or not do it for any boot (including cold boot)?
I do like this idea! I couldn't find this in the git history, but do you know if this was added in the linux kernel just because EFI spec added support for it, or if there was a specific security problem?
Thanks!
Ard Biesheuvel
maintainerRe: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 75 lines · Usama Arif
Quoted 61 lines · Ard Biesheuvel
Quoted 51 lines · Usama Arif
Quoted 47 lines · Ard Biesheuvel
Quoted 45 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)Quoted 6 lines
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use
e820_table_firmware?No, I mean kexec ignores the memory attributes table.
Quoted 9 lines
Quoted 2 lines
Also a very basic question, what do you mean by run with the firmware RWX?
The memory attributes table is an overlay for the EFI memory map that describes which runtime code regions may be mapped with restricted permissions. Without this table, everything will be mapped writable as well as executable, but only in the EFI page tables, which are only active when an EFI call is in progress.
Quoted 6 lines
Thanks for explaining!
So basically get rid of
memattr.c:)Do you mean get rid of it only for kexec, or not do it for any boot (including cold boot)?
Only for kexec, and only on x86
Quoted 5 lines
I do like this idea! I couldn't find this in the git history, but do you know if this was added in the linux kernel just because EFI spec added support for it, or if there was a specific security problem?
Mapping memory RWX is generally a bad idea, so we should avoid it if possible. But EFI runtime memory regions are only mapped during a EFI runtime call, and these don't happen often at all, so the benefit is only marginal. (In the early days of EFI, it was more common for the OS to map these regions permanently, but we stopped doing that a long time ago)
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
In reply to Usama ArifQuoted 77 lines · Usama Arif
Quoted 61 lines · Ard Biesheuvel
Quoted 51 lines · Usama Arif
Quoted 47 lines · Ard Biesheuvel
Quoted 45 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)Quoted 6 lines
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use
e820_table_firmware?No, I mean kexec ignores the memory attributes table.
Quoted 9 lines
Quoted 2 lines
Also a very basic question, what do you mean by run with the firmware RWX?
The memory attributes table is an overlay for the EFI memory map that describes which runtime code regions may be mapped with restricted permissions. Without this table, everything will be mapped writable as well as executable, but only in the EFI page tables, which are only active when an EFI call is in progress.
Thanks for explaining!
Quoted 9 lines
So basically get rid of
memattr.c:)Do you mean get rid of it only for kexec, or not do it for any boot (including cold boot)?
I do like this idea! I couldn't find this in the git history, but do you know if this was added in the linux kernel just because EFI spec added support for it, or if there was a specific security problem?
Usama, can you try the patch below?
[ format is wrong due to webmail corruption. But if it works I can send a formal patch later ]
$ git diff arch/x86
arch/x86/platform/efi/quirks.c +4 -0
@@ -561,6 +561,11 @@ int __init efi_reuse_config(u64 tables, int nr_tables)if (!efi_guidcmp (guid,SMBIOS_TABLE_GUID )) ((efi_config_table_64_t *)p)->table = data->smbios; + +/* Not bother to play with mem attr table across kexec */ +if (!efi_guidcmp (guid,EFI_MEMORY_ATTRIBUTES_TABLE_GUID )) + ((efi_config_table_64_t *)p)->table =
EFI_INVALID_TABLE_ADDR;
+
p += sz;
}Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 100 lines · Dave Young
Quoted 77 lines · Usama Arif
Quoted 61 lines · Ard Biesheuvel
Quoted 51 lines · Usama Arif
Quoted 47 lines · Ard Biesheuvel
Quoted 45 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)Quoted 6 lines
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use
e820_table_firmware?No, I mean kexec ignores the memory attributes table.
Quoted 9 lines
Quoted 2 lines
Also a very basic question, what do you mean by run with the firmware RWX?
The memory attributes table is an overlay for the EFI memory map that describes which runtime code regions may be mapped with restricted permissions. Without this table, everything will be mapped writable as well as executable, but only in the EFI page tables, which are only active when an EFI call is in progress.
Thanks for explaining!
Quoted 9 lines
So basically get rid of
memattr.c:)Do you mean get rid of it only for kexec, or not do it for any boot (including cold boot)?
I do like this idea! I couldn't find this in the git history, but do you know if this was added in the linux kernel just because EFI spec added support for it, or if there was a specific security problem?Usama, can you try the patch below?
[ format is wrong due to webmail corruption. But if it works I can send a formal patch later ]$ git diff arch/x86arch/x86/platform/efi/quirks.c +0
-0@@ -561,6 +561,11 @@ int __init efi_reuse_config(u64 tables, int nr_tables)
arch/x86/platform/efi/quirks.c int __init efi_reuse_config(u64 tables, int nr_tables) · line 571
Quoted 10 lines
arch/x86/platform/efi/quirks.c +5
-0if (!efi_guidcmp (guid,SMBIOS_TABLE_GUID )) ((efi_config_table_64_t *)p)->table = data->smbios; + +/* Not bother to play with mem attr table across kexec */ +if (!efi_guidcmp (guid,EFI_MEMORY_ATTRIBUTES_TABLE_GUID )) + ((efi_config_table_64_t *)p)->table =EFI_INVALID_TABLE_ADDR ; + p += sz; }
This would work, I am guessing it will have a similar effect to what I sent last week in
https://lore.kernel.org/all/[email protected]/
I think it needs to be wrapped in ifdef CONFIG_X86_64.
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 118 lines · Usama Arif
Quoted 100 lines · Dave Young
Quoted 77 lines · Usama Arif
Quoted 61 lines · Ard Biesheuvel
Quoted 51 lines · Usama Arif
Quoted 47 lines · Ard Biesheuvel
Quoted 45 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)Quoted 6 lines
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use
e820_table_firmware?No, I mean kexec ignores the memory attributes table.
Quoted 9 lines
Quoted 2 lines
Also a very basic question, what do you mean by run with the firmware RWX?
The memory attributes table is an overlay for the EFI memory map that describes which runtime code regions may be mapped with restricted permissions. Without this table, everything will be mapped writable as well as executable, but only in the EFI page tables, which are only active when an EFI call is in progress.
Thanks for explaining!
Quoted 9 lines
So basically get rid of
memattr.c:)Do you mean get rid of it only for kexec, or not do it for any boot (including cold boot)?
I do like this idea! I couldn't find this in the git history, but do you know if this was added in the linux kernel just because EFI spec added support for it, or if there was a specific security problem?Usama, can you try the patch below?
[ format is wrong due to webmail corruption. But if it works I can send a formal patch later ]$ git diff arch/x86arch/x86/platform/efi/quirks.c +0
-0@@ -561,6 +561,11 @@ int __init efi_reuse_config(u64 tables, int nr_tables)arch/x86/platform/efi/quirks.c int __init efi_reuse_config(u64 tables, int nr_tables) · line 571
Quoted 10 lines
arch/x86/platform/efi/quirks.c +5
-0if (!efi_guidcmp (guid,SMBIOS_TABLE_GUID )) ((efi_config_table_64_t *)p)->table = data->smbios; + +/* Not bother to play with mem attr table across kexec */ +if (!efi_guidcmp (guid,EFI_MEMORY_ATTRIBUTES_TABLE_GUID )) + ((efi_config_table_64_t *)p)->table =EFI_INVALID_TABLE_ADDR ; + p += sz; }This would work, I am guessing it will have a similar effect to what I sent last week in
https://lore.kernel.org/all/[email protected]/
Quoted 2 lines
I think it needs to be wrapped in ifdef
CONFIG_X86_64.
IMO we should consider the 2 patches in this series first before disabling it for kexec. These patches actually fix the issue.
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 121 lines · Usama Arif
Quoted 118 lines · Usama Arif
Quoted 100 lines · Dave Young
Quoted 77 lines · Usama Arif
Quoted 61 lines · Ard Biesheuvel
Quoted 51 lines · Usama Arif
Quoted 47 lines · Ard Biesheuvel
Quoted 45 lines · Usama Arif
The commit in [1] introduced a check to see if EFI memory attributes table was corrupted. It assumed that efi.memmap.nr_map remains constant, but it changes during late boot.
Hence, the check is valid during cold boot, but not in the subsequent kexec boot.This is best explained with an exampled. At cold boot, for a test machine:
efi.memmap.nr_map=91, memory_attributes_table->num_entries=48,desc_size= 48
Hence, the check introduced in [1] where 3x the size of the entire EFI memory map is a reasonable upper bound for the size of this table is valid.In late boot
__efi_enter_virtual_modecalls 2 functions that updates efi.memmap.nr_map:
-efi_map_regionswhich reduces thecountof map entries
(for e.g. ifshould_map_regionreturns false) and which is reflected in efi.memmap by__efi_memmap_init.
At this point efi.memmap.nr_map becomes 46 in the test machine.
-efi_free_boot_serviceswhich also reduces the number of memory regions available (for e.g. ifmd->typeormd->attributeis not the right value). At this point efi.memmap.nr_map becomes 9 in the test machine.
Hence when you kexec into a new kernel and pass efi.memmap, the paramaters that are compared are:
efi.memmap.nr_map=9,
memory_attributes_table->num_entries=48,desc_size= 48
where the check in [1] is no longer valid with such a low efi.memmap.nr_map as it was reduced due toefi_map_regionsandefi_free_boot_services.A more appropriate check is to see if the description size reported by efi and memory attributes table is the same.
[1] https://lore.kernel.org/all/[email protected]/
Fixes 8fbe4c49c0cc ("efi/memattr: Ignore table if the size is clearly bogus")Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- drivers/firmware/efi/memattr.c | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-)Quoted 6 lines
Quoted 3 lines
The more I think about this, the more I feel that kexec on x86 should simply discard this table, and run with the firmware code RWX (which is not the end of the world).
By discard this table, do you mean kexec not use
e820_table_firmware?No, I mean kexec ignores the memory attributes table.
Quoted 9 lines
Quoted 2 lines
Also a very basic question, what do you mean by run with the firmware RWX?
The memory attributes table is an overlay for the EFI memory map that describes which runtime code regions may be mapped with restricted permissions. Without this table, everything will be mapped writable as well as executable, but only in the EFI page tables, which are only active when an EFI call is in progress.
Thanks for explaining!
Quoted 9 lines
So basically get rid of
memattr.c:)Do you mean get rid of it only for kexec, or not do it for any boot (including cold boot)?
I do like this idea! I couldn't find this in the git history, but do you know if this was added in the linux kernel just because EFI spec added support for it, or if there was a specific security problem?Usama, can you try the patch below?
[ format is wrong due to webmail corruption. But if it works I can send a formal patch later ]$ git diff arch/x86arch/x86/platform/efi/quirks.c +0
-0@@ -561,6 +561,11 @@ int __init efi_reuse_config(u64 tables, int nr_tables)arch/x86/platform/efi/quirks.c int __init efi_reuse_config(u64 tables, int nr_tables) · line 571
Quoted 10 lines
arch/x86/platform/efi/quirks.c +5
-0if (!efi_guidcmp (guid,SMBIOS_TABLE_GUID )) ((efi_config_table_64_t *)p)->table = data->smbios; + +/* Not bother to play with mem attr table across kexec */ +if (!efi_guidcmp (guid,EFI_MEMORY_ATTRIBUTES_TABLE_GUID )) + ((efi_config_table_64_t *)p)->table =EFI_INVALID_TABLE_ADDR ; + p += sz; }This would work, I am guessing it will have a similar effect to what I sent last week in
https://lore.kernel.org/all/[email protected]/
Quoted 6 lines
Quoted 2 lines
I think it needs to be wrapped in ifdef
CONFIG_X86_64.IMO we should consider the 2 patches in this series first before disabling it for kexec. These patches actually fix the issue.
Hi Ard,
Just wanted to check how should we proceed forward? Should we try and fix the warning and corruption during kexec as done in this series or not initialize memory attributes table at all in kexec boot? I would prefer fixing the issues as in this series.
Thanks,
Usama
Ard Biesheuvel
maintainerRe: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 2 lines · Usama Arif
...
Quoted 6 lines
Hi Ard,
Just wanted to check how should we proceed forward? Should we try and fix the warning and corruption during kexec as done in this series or not initialize memory attributes table at all in kexec boot? I would prefer fixing the issues as in this series.
I would prefer kexec boot on x86 to disregard the memory attributes table entirely.
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 6 lines · Ard Biesheuvel
Quoted 2 lines · Usama Arif
...
Quoted 2 lines
Hi Ard,
Quoted 7 lines
Quoted 4 lines
Just wanted to check how should we proceed forward? Should we try and fix the warning and corruption during kexec as done in this series or not initialize memory attributes table at all in kexec boot? I would prefer fixing the issues as in this series.
I would prefer kexec boot on x86 to disregard the memory attributes table entirely.
Would you like Dave to send something like
https://lore.kernel.org/all/CALu+AoS8tb=HgaybDw5OG4A1QbOXHvuidpu0ynmz-nE1nBqzTA@mail.gmail.com/
on the mailing list (wrapped in ifdef CONFIG_X86_64)
or we could do
https://lore.kernel.org/all/[email protected]/
as well.
Or if there is any other way you prefer, I am happy to implement and test.
Thanks,
Usama
Ard Biesheuvel
maintainerRe: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 15 lines · Usama Arif
Quoted 11 lines · Ard Biesheuvel
Quoted 2 lines · Usama Arif
...
Quoted 6 lines
Hi Ard,
Just wanted to check how should we proceed forward? Should we try and fix the warning and corruption during kexec as done in this series or not initialize memory attributes table at all in kexec boot? I would prefer fixing the issues as in this series.
Quoted 7 lines
Quoted 2 lines
I would prefer kexec boot on x86 to disregard the memory attributes table entirely.
Would you like Dave to send something like
https://lore.kernel.org/all/CALu+AoS8tb=HgaybDw5OG4A1QbOXHvuidpu0ynmz-nE1nBqzTA@mail.gmail.com/
on the mailing list (wrapped in ifdefCONFIG_X86_64)
I prefer this approach. and no need for the ifdef, this is x86 specific code, and the memory attributes table is already ignored entirely on 32-bit x86 iirc
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 19 lines · Ard Biesheuvel
Quoted 18 lines · Usama Arif
Quoted 13 lines · Ard Biesheuvel
Quoted 2 lines · Usama Arif
...
Quoted 6 lines
Hi Ard,
Just wanted to check how should we proceed forward? Should we try and fix the warning and corruption during kexec as done in this series or not initialize memory attributes table at all in kexec boot? I would prefer fixing the issues as in this series.
I would prefer kexec boot on x86 to disregard the memory attributes table entirely.
Quoted 8 lines
Quoted 4 lines
Would you like Dave to send something like
https://lore.kernel.org/all/CALu+AoS8tb=HgaybDw5OG4A1QbOXHvuidpu0ynmz-nE1nBqzTA@mail.gmail.com/
on the mailing list (wrapped in ifdefCONFIG_X86_64)I prefer this approach. and no need for the ifdef, this is x86 specific code, and the memory attributes table is already ignored entirely on 32-bit x86 iirc
ah yes, I ignored the file name when reviewing it and just focused on the function :)
Will wait for Dave to send it.
Thanks,
Usama
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Hi,
Quoted 28 lines · Usama Arif
Quoted 24 lines · Ard Biesheuvel
Quoted 22 lines · Usama Arif
Quoted 6 lines · Ard Biesheuvel
Quoted 2 lines · Usama Arif
...
Quoted 2 lines
Hi Ard,
Quoted 7 lines
Quoted 4 lines
Just wanted to check how should we proceed forward? Should we try and fix the warning and corruption during kexec as done in this series or not initialize memory attributes table at all in kexec boot? I would prefer fixing the issues as in this series.
I would prefer kexec boot on x86 to disregard the memory attributes table entirely.
Would you like Dave to send something like
https://lore.kernel.org/all/CALu+AoS8tb=HgaybDw5OG4A1QbOXHvuidpu0ynmz-nE1nBqzTA@mail.gmail.com/
on the mailing list (wrapped in ifdefCONFIG_X86_64)
Quoted 7 lines
Quoted 3 lines
I prefer this approach. and no need for the ifdef, this is x86 specific code, and the memory attributes table is already ignored entirely on 32-bit x86 iirc
ah yes, I ignored the file name when reviewing it and just focused on the function :)
Will wait for Dave to send it.
Ok, I will add reported-by from you and suggested-by from Ard. But I can not test the efi mem attr, I'd prefer to have your test results first. Could you confirm that?
Thanks
Dave
Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Quoted 34 lines · Dave Young
Hi,
Quoted 32 lines · Usama Arif
Quoted 27 lines · Ard Biesheuvel
Quoted 15 lines · Usama Arif
Quoted 11 lines · Ard Biesheuvel
Quoted 2 lines · Usama Arif
...
Quoted 6 lines
Hi Ard,
Just wanted to check how should we proceed forward? Should we try and fix the warning and corruption during kexec as done in this series or not initialize memory attributes table at all in kexec boot? I would prefer fixing the issues as in this series.
Quoted 7 lines
Quoted 2 lines
I would prefer kexec boot on x86 to disregard the memory attributes table entirely.
Would you like Dave to send something like
https://lore.kernel.org/all/CALu+AoS8tb=HgaybDw5OG4A1QbOXHvuidpu0ynmz-nE1nBqzTA@mail.gmail.com/
on the mailing list (wrapped in ifdefCONFIG_X86_64)I prefer this approach. and no need for the ifdef, this is x86 specific code, and the memory attributes table is already ignored entirely on 32-bit x86 iirc
Quoted 8 lines
Quoted 3 lines
ah yes, I ignored the file name when reviewing it and just focused on the function :)
Will wait for Dave to send it.
Ok, I will add reported-by from you and suggested-by from Ard. But I can not test the efi mem attr, I'd prefer to have your test results first. Could you confirm that?
Please also add Reported-by: Breno Leitao <[email protected]> who originally discovered and reported the issue.
I have tested it and it works, efi_memattr_init will just return 0 as efi_mem_attr_table = EFI_INVALID_TABLE_ADDR, so it won't be initialized. Feel free to add Tested-by tag from me.
Thanks,
Usama
RFC 2/2 efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
In reply to Usama ArifWhen this area is not reserved, it comes up as usable in /sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region where efi_mem_attr_table is and overwrite it and relocate_kernel.
Since the patch in [1] was merged, all boots after kexec are producing the warning that it introduced.
Having a fix in firmware can be difficult to get through. The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service call option [3], [4], and install_configuration_table does not seem to work as a valid substitute.
As a last option for a fix, this patch marks that region as reserved in e820_table_firmware if it is currently E820_TYPE_RAM so that kexec doesn't use it for kernel segments.
[1] https://lore.kernel.org/all/[email protected]/
[2] https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Misc/MemoryAttributesTable.c#L100
[3] https://github.com/tianocore/edk2/blob/42a141800c0c26a09d2344e84a89ce4097a263ae/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c#L41
[4] https://elixir.bootlin.com/linux/v6.12.6/source/drivers/firmware/efi/libstub/efistub.h#L327
--- arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/e820.c | 6 ++++++ arch/x86/platform/efi/efi.c | 9 +++++++++ drivers/firmware/efi/memattr.c | 1 + include/linux/efi.h | 7 +++++++ 5 files changed, 25 insertions(+)
arch/x86/include/asm/e820/api.h +2 -0
@@ -16,6 +16,8 @@ extern bool e820__mapped_all(u64 start, u64 end, enum e820_type type);extern void e820__range_add (u64 start,u64 size,enum e820_type type);extern u64 e820__range_update (u64 start,u64 size,enum e820_type old_type,enum e820_type new_type); +extern u64 e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type);extern u64 e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type);extern u64 e820__range_update_table (struct e820_table *t,u64 start,u64 size,enum e820_type old_type,enum e820_type new_type);
arch/x86/kernel/e820.c +6 -0
@@ -538,6 +538,12 @@ u64 __init e820__range_update_table(struct e820_table *t, u64 start, u64 size,return __e820__range_update (t, start, size, old_type, new_type); } +u64 __init e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type) +{ +return __e820__range_update (e820_table_firmware, start, size, old_type, new_type); +} +/* Remove a range of memory from the E820 table: */ u64 __init e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type) {
arch/x86/platform/efi/efi.c +9 -0
@@ -168,6 +168,15 @@ static void __init do_add_efi_memmap(void)e820__update_table (e820_table); } +/* Reserve firmware area if it was marked as RAM */ +void arch_update_firmware_area (u64 addr,u64 size) +{ +if (e820__get_entry_type (addr, addr + size) ==E820_TYPE_RAM ) { +e820__range_update_firmware (addr, size,E820_TYPE_RAM ,E820_TYPE_RESERVED ); +e820__update_table (e820_table_firmware); + } +} +/* * Given add_efi_memmap defaults to 0 and there is no alternative * e820 mechanism for soft-reserved memory, import the full EFI memory
drivers/firmware/efi/memattr.c +1 -0
@@ -53,6 +53,7 @@ int __init efi_memattr_init(void) size = tbl->num_entries * tbl->desc_size; tbl_size =sizeof (*tbl) + size;memblock_reserve (efi_mem_attr_table, tbl_size); +arch_update_firmware_area (efi_mem_attr_table, tbl_size);set_bit (EFI_MEM_ATTR , &efi.flags); unmap:
include/linux/efi.h +7 -0
@@ -1358,4 +1358,11 @@ extern struct blocking_notifier_head efivar_ops_nh;void efivars_generic_ops_register (void );void efivars_generic_ops_unregister (void ); +#ifdef CONFIG_X86_64 +void __init arch_update_firmware_area (u64 addr,u64 size); +#else +static inline void __init arch_update_firmware_area (u64 addr,u64 size) +{ +} +#endif #endif /* _LINUX_EFI_H */
Signature · 1 line
2.43.5
Ard Biesheuvel
maintainerRe: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 10 lines · Usama Arif
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.Since the patch in [1] was merged, all boots after kexec are producing the warning that it introduced.
Having a fix in firmware can be difficult to get through.
I don't follow. I don't think there is anything wrong with the firmware here. Could you elaborate?
Quoted 5 lines
The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service call option [3], [4], and
install_configuration_tabledoes not seem to work as a valid substitute.
To do what, exactly?
Quoted 100 lines
As a last option for a fix, this patch marks that region as reserved in
e820_table_firmwareif it is currentlyE820_TYPE_RAMso that kexec doesn't use it for kernel segments.[1] https://lore.kernel.org/all/[email protected]/
[2] https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Misc/MemoryAttributesTable.c#L100
[3] https://github.com/tianocore/edk2/blob/42a141800c0c26a09d2344e84a89ce4097a263ae/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c#L41
[4] https://elixir.bootlin.com/linux/v6.12.6/source/drivers/firmware/efi/libstub/efistub.h#L327Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/e820.c | 6 ++++++ arch/x86/platform/efi/efi.c | 9 +++++++++ drivers/firmware/efi/memattr.c | 1 + include/linux/efi.h | 7 +++++++ 5 files changed, 25 insertions(+)arch/x86/include/asm/e820/api.h +2
-0@@ -16,6 +16,8 @@ extern bool e820__mapped_all(u64 start, u64 end, enum e820_type type);extern void e820__range_add (u64 start,u64 size,enum e820_type type);extern u64 e820__range_update (u64 start,u64 size,enum e820_type old_type,enum e820_type new_type); +extern u64 e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type);extern u64 e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type);extern u64 e820__range_update_table (struct e820_table *t,u64 start,u64 size,enum e820_type old_type,enum e820_type new_type);arch/x86/kernel/e820.c +6
-0@@ -538,6 +538,12 @@ u64 __init e820__range_update_table(struct e820_table *t, u64 start, u64 size,return __e820__range_update (t, start, size, old_type, new_type); } +u64 __init e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type) +{ +return __e820__range_update (e820_table_firmware, start, size, old_type, new_type); +} +/* Remove a range of memory from the E820 table: */ u64 __init e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type) {arch/x86/platform/efi/efi.c +9
-0@@ -168,6 +168,15 @@ static void __init do_add_efi_memmap(void)e820__update_table (e820_table); } +/* Reserve firmware area if it was marked as RAM */ +void arch_update_firmware_area (u64 addr,u64 size) +{ +if (e820__get_entry_type (addr, addr + size) ==E820_TYPE_RAM ) { +e820__range_update_firmware (addr, size,E820_TYPE_RAM ,E820_TYPE_RESERVED ); +e820__update_table (e820_table_firmware); + } +} +/* * Given add_efi_memmap defaults to 0 and there is no alternative * e820 mechanism for soft-reserved memory, import the full EFI memory drivers/firmware/efi/memattr.c +1
-0@@ -53,6 +53,7 @@ int __init efi_memattr_init(void) size = tbl->num_entries * tbl->desc_size; tbl_size =sizeof (*tbl) + size;memblock_reserve (efi_mem_attr_table, tbl_size); +arch_update_firmware_area (efi_mem_attr_table, tbl_size);set_bit (EFI_MEM_ATTR , &efi.flags); unmap:include/linux/efi.h +7
-1@@ -1358,4 +1358,11 @@ extern struct blocking_notifier_head efivar_ops_nh;void efivars_generic_ops_register (void );void efivars_generic_ops_unregister (void ); +#ifdef CONFIG_X86_64 +void __init arch_update_firmware_area (u64 addr,u64 size); +#else +static inline void __init arch_update_firmware_area (u64 addr,u64 size) +{ +} +#endif #endif /* _LINUX_EFI_H */ --2.43.5
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 7 lines · Ard Biesheuvel
Quoted 6 lines · Usama Arif
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.
Quoted 8 lines
Quoted 4 lines
Since the patch in [1] was merged, all boots after kexec are producing the warning that it introduced.
Having a fix in firmware can be difficult to get through.
I don't follow. I don't think there is anything wrong with the firmware here. Could you elaborate?
So the problem is, kexec sees this memory as System RAM, and decides it can be used to place an image here.
I guess the question is (and I actually don't know the answer here), whose responsibility is it to mark this region as reserved so that its not touched by anyone else. I would have thought it should be firmware?
Maybe its not the firmwares' job to mark it as reserved, but just pass it to kernel and the kernel is supposed to make sure it gets reserved in a proper way, even across kexecs.
I think in the end whoevers' responsibility it is, the easiest path forward seems to be in kernel? (and not firmware or libstub)
Quoted 9 lines
Quoted 6 lines
The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service call option [3], [4], and
install_configuration_tabledoes not seem to work as a valid substitute.To do what, exactly?
To change the memory type from System RAM to either reserved or something more appropriate, i.e. any type that is not touched by kexec or any other userspace.
Basically the example code I attached at the end of the cover letter in
https://lore.kernel.org/all/[email protected]/
It could be EFI_ACPI_RECLAIM_MEMORY or EFI_RESERVED_TYPE, both of which aren't touched by kexec.
Quoted 100 lines
Quoted 100 lines
As a last option for a fix, this patch marks that region as reserved in
e820_table_firmwareif it is currentlyE820_TYPE_RAMso that kexec doesn't use it for kernel segments.[1] https://lore.kernel.org/all/[email protected]/
[2] https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Misc/MemoryAttributesTable.c#L100
[3] https://github.com/tianocore/edk2/blob/42a141800c0c26a09d2344e84a89ce4097a263ae/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c#L41
[4] https://elixir.bootlin.com/linux/v6.12.6/source/drivers/firmware/efi/libstub/efistub.h#L327Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/e820.c | 6 ++++++ arch/x86/platform/efi/efi.c | 9 +++++++++ drivers/firmware/efi/memattr.c | 1 + include/linux/efi.h | 7 +++++++ 5 files changed, 25 insertions(+)arch/x86/include/asm/e820/api.h +2
-0@@ -16,6 +16,8 @@ extern bool e820__mapped_all(u64 start, u64 end, enum e820_type type);extern void e820__range_add (u64 start,u64 size,enum e820_type type);extern u64 e820__range_update (u64 start,u64 size,enum e820_type old_type,enum e820_type new_type); +extern u64 e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type);extern u64 e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type);extern u64 e820__range_update_table (struct e820_table *t,u64 start,u64 size,enum e820_type old_type,enum e820_type new_type);arch/x86/kernel/e820.c +6
-0@@ -538,6 +538,12 @@ u64 __init e820__range_update_table(struct e820_table *t, u64 start, u64 size,return __e820__range_update (t, start, size, old_type, new_type); } +u64 __init e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type) +{ +return __e820__range_update (e820_table_firmware, start, size, old_type, new_type); +} +/* Remove a range of memory from the E820 table: */ u64 __init e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type) {arch/x86/platform/efi/efi.c +9
-0@@ -168,6 +168,15 @@ static void __init do_add_efi_memmap(void)e820__update_table (e820_table); } +/* Reserve firmware area if it was marked as RAM */ +void arch_update_firmware_area (u64 addr,u64 size) +{ +if (e820__get_entry_type (addr, addr + size) ==E820_TYPE_RAM ) { +e820__range_update_firmware (addr, size,E820_TYPE_RAM ,E820_TYPE_RESERVED ); +e820__update_table (e820_table_firmware); + } +} +/* * Given add_efi_memmap defaults to 0 and there is no alternative * e820 mechanism for soft-reserved memory, import the full EFI memory drivers/firmware/efi/memattr.c +1
-0@@ -53,6 +53,7 @@ int __init efi_memattr_init(void) size = tbl->num_entries * tbl->desc_size; tbl_size =sizeof (*tbl) + size;memblock_reserve (efi_mem_attr_table, tbl_size); +arch_update_firmware_area (efi_mem_attr_table, tbl_size);set_bit (EFI_MEM_ATTR , &efi.flags); unmap:include/linux/efi.h +7
-1@@ -1358,4 +1358,11 @@ extern struct blocking_notifier_head efivar_ops_nh;void efivars_generic_ops_register (void );void efivars_generic_ops_unregister (void ); +#ifdef CONFIG_X86_64 +void __init arch_update_firmware_area (u64 addr,u64 size); +#else +static inline void __init arch_update_firmware_area (u64 addr,u64 size) +{ +} +#endif #endif /* _LINUX_EFI_H */ --2.43.5
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 22 lines · Usama Arif
Quoted 7 lines · Ard Biesheuvel
Quoted 6 lines · Usama Arif
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.Quoted 8 lines
Quoted 4 lines
Since the patch in [1] was merged, all boots after kexec are producing the warning that it introduced.
Having a fix in firmware can be difficult to get through.
I don't follow. I don't think there is anything wrong with the firmware here. Could you elaborate?
So the problem is, kexec sees this memory as System RAM, and decides it can be used to place an image here.
Quoted 8 lines
I guess the question is (and I actually don't know the answer here), whose responsibility is it to mark this region as reserved so that its not touched by anyone else. I would have thought it should be firmware?
Maybe its not the firmwares' job to mark it as reserved, but just pass it to kernel and the kernel is supposed to make sure it gets reserved in a proper way, even across kexecs.
Reservation is a kernel concept, the firmware/EFI etc give the kernel guidance - but the actual maps here are largely informational and the kernel can do whatever it wants (within reason).
So what you're really saying is either
a) the hardware is mis-reporting the memory map configurations (e.g. some EFI_* bit is missing), or
b) the kernel isn't doing the right thing.
I believe Ard is pointing out that the additional map abstraction is just trying to retain a "current" versus "original" configuration - and this is more of a headache than it is worth as it appears to be causing confusion as to which one should be respected across kexec.
So the separate maps should just be one, and we should just smash the "original" configuration rather than keeping a copy.
Please correct me if i'm misunderstanding anything.
Quoted 124 lines
I think in the end whoevers' responsibility it is, the easiest path forward seems to be in kernel? (and not firmware or libstub)
Quoted 9 lines
Quoted 6 lines
The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service call option [3], [4], and
install_configuration_tabledoes not seem to work as a valid substitute.To do what, exactly?
To change the memory type from System RAM to either reserved or something more appropriate, i.e. any type that is not touched by kexec or any other userspace.
Basically the example code I attached at the end of the cover letter in
https://lore.kernel.org/all/[email protected]/
It could beEFI_ACPI_RECLAIM_MEMORYorEFI_RESERVED_TYPE, both of which aren't touched by kexec.Quoted 100 lines
Quoted 100 lines
As a last option for a fix, this patch marks that region as reserved in
e820_table_firmwareif it is currentlyE820_TYPE_RAMso that kexec doesn't use it for kernel segments.[1] https://lore.kernel.org/all/[email protected]/
[2] https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Misc/MemoryAttributesTable.c#L100
[3] https://github.com/tianocore/edk2/blob/42a141800c0c26a09d2344e84a89ce4097a263ae/MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c#L41
[4] https://elixir.bootlin.com/linux/v6.12.6/source/drivers/firmware/efi/libstub/efistub.h#L327Reported-by Breno Leitao <[email protected]>Signed-off-by Usama Arif <[email protected]>--- arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/e820.c | 6 ++++++ arch/x86/platform/efi/efi.c | 9 +++++++++ drivers/firmware/efi/memattr.c | 1 + include/linux/efi.h | 7 +++++++ 5 files changed, 25 insertions(+)arch/x86/include/asm/e820/api.h +2
-0@@ -16,6 +16,8 @@ extern bool e820__mapped_all(u64 start, u64 end, enum e820_type type);extern void e820__range_add (u64 start,u64 size,enum e820_type type);extern u64 e820__range_update (u64 start,u64 size,enum e820_type old_type,enum e820_type new_type); +extern u64 e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type);extern u64 e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type);extern u64 e820__range_update_table (struct e820_table *t,u64 start,u64 size,enum e820_type old_type,enum e820_type new_type);arch/x86/kernel/e820.c +6
-0@@ -538,6 +538,12 @@ u64 __init e820__range_update_table(struct e820_table *t, u64 start, u64 size,return __e820__range_update (t, start, size, old_type, new_type); } +u64 __init e820__range_update_firmware (u64 start,u64 size,enum e820_type old_type, +enum e820_type new_type) +{ +return __e820__range_update (e820_table_firmware, start, size, old_type, new_type); +} +/* Remove a range of memory from the E820 table: */ u64 __init e820__range_remove (u64 start,u64 size,enum e820_type old_type,bool check_type) {arch/x86/platform/efi/efi.c +9
-0@@ -168,6 +168,15 @@ static void __init do_add_efi_memmap(void)e820__update_table (e820_table); } +/* Reserve firmware area if it was marked as RAM */ +void arch_update_firmware_area (u64 addr,u64 size) +{ +if (e820__get_entry_type (addr, addr + size) ==E820_TYPE_RAM ) { +e820__range_update_firmware (addr, size,E820_TYPE_RAM ,E820_TYPE_RESERVED ); +e820__update_table (e820_table_firmware); + } +} +/* * Given add_efi_memmap defaults to 0 and there is no alternative * e820 mechanism for soft-reserved memory, import the full EFI memory drivers/firmware/efi/memattr.c +1
-0@@ -53,6 +53,7 @@ int __init efi_memattr_init(void) size = tbl->num_entries * tbl->desc_size; tbl_size =sizeof (*tbl) + size;memblock_reserve (efi_mem_attr_table, tbl_size); +arch_update_firmware_area (efi_mem_attr_table, tbl_size);set_bit (EFI_MEM_ATTR , &efi.flags); unmap:include/linux/efi.h +7
-1@@ -1358,4 +1358,11 @@ extern struct blocking_notifier_head efivar_ops_nh;void efivars_generic_ops_register (void );void efivars_generic_ops_unregister (void ); +#ifdef CONFIG_X86_64 +void __init arch_update_firmware_area (u64 addr,u64 size); +#else +static inline void __init arch_update_firmware_area (u64 addr,u64 size) +{ +} +#endif #endif /* _LINUX_EFI_H */ --2.43.5
Ard Biesheuvel
maintainerRe: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
In reply to Usama ArifQuoted 20 lines · Usama Arif
Quoted 7 lines · Ard Biesheuvel
Quoted 6 lines · Usama Arif
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.Quoted 8 lines
Quoted 4 lines
Since the patch in [1] was merged, all boots after kexec are producing the warning that it introduced.
Having a fix in firmware can be difficult to get through.
I don't follow. I don't think there is anything wrong with the firmware here. Could you elaborate?
Quoted 8 lines
So the problem is, kexec sees this memory as System RAM, and decides it can be used to place an image here.
I guess the question is (and I actually don't know the answer here), whose responsibility is it to mark this region as reserved so that its not touched by anyone else. I would have thought it should be firmware?
No, it is the OS. The firmware only reserves regions that are needed for its own correct operation at runtime. For informational tables such as this one, it is up to the OS whether it wants to reserve it and keep it in place, consume it and release the memory, or ignore it altogether.
Quoted 4 lines
Maybe its not the firmwares' job to mark it as reserved, but just pass it to kernel and the kernel is supposed to make sure it gets reserved in a proper way, even across kexecs.
Indeed.
Quoted 3 lines
I think in the end whoevers' responsibility it is, the easiest path forward seems to be in kernel? (and not firmware or libstub)
Agreed. But as I pointed out in the other thread, the memory attributes table only augments the memory map with permission information, and can be disregarded, and given how badly we mangle the memory map on x86, maybe this is the right choice here.
Quoted 10 lines
Quoted 9 lines
Quoted 6 lines
The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service call option [3], [4], and
install_configuration_tabledoes not seem to work as a valid substitute.To do what, exactly?
Quoted 9 lines
To change the memory type from System RAM to either reserved or something more appropriate, i.e. any type that is not touched by kexec or any other userspace.
Basically the example code I attached at the end of the cover letter in
https://lore.kernel.org/all/[email protected]/
It could beEFI_ACPI_RECLAIM_MEMORYorEFI_RESERVED_TYPE, both of which aren't touched by kexec.
This is a kexec problem (on x86 only) so let's fix it there.
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Hello Ard,
Quoted 10 lines · Ard Biesheuvel
Quoted 3 lines · Usama Arif
I think in the end whoevers' responsibility it is, the easiest path forward seems to be in kernel? (and not firmware or libstub)
Agreed. But as I pointed out in the other thread, the memory attributes table only augments the memory map with permission information, and can be disregarded, and given how badly we mangle the memory map on x86, maybe this is the right choice here.
If this augmented memory is not preserved accross kexec, then the next kexec'ed kernel will be able to find the original table?
I understand that the memattr region(s) need to be always (in each kexec instances) memblocked_reserved to protect it from being used as a System RAM, right?
Thus, if it is not passed throught e820, kexec'ed kernel needs to fetch it again from original EFI table at kexec/boot time.
This brings me another question.
If the kexec'ed kernel sees the original memory, why can't it augment/update the RX permissions *again*, instead of passing the previous augmented version from previous kernel in this crazy dance.
Quoted 1 line
This is a kexec problem (on x86 only) so let's fix it there.
Would you mind explaining what kexec needs to be done differently? Should it preserve the augmented memattr table independently if it is mapped in e820?
Thank you!
--breno
Ard Biesheuvel
maintainerRe: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 18 lines · Breno Leitao
Hello Ard,
Quoted 10 lines · Ard Biesheuvel
Quoted 3 lines · Usama Arif
I think in the end whoevers' responsibility it is, the easiest path forward seems to be in kernel? (and not firmware or libstub)
Agreed. But as I pointed out in the other thread, the memory attributes table only augments the memory map with permission information, and can be disregarded, and given how badly we mangle the memory map on x86, maybe this is the right choice here.
If this augmented memory is not preserved accross kexec, then the next kexec'ed kernel will be able to find the original table?
Quoted 7 lines
I understand that the memattr region(s) need to be always (in each kexec instances)
memblocked_reservedto protect it from being used as a System RAM, right?Thus, if it is not passed throught e820, kexec'ed kernel needs to fetch it again from original EFI table at kexec/boot time.
Not sure what 'fetching' means here.
Quoted 6 lines
This brings me another question.
If the kexec'ed kernel sees the original memory, why can't it augment/update the RX permissions *again*, instead of passing the previous augmented version from previous kernel in this crazy dance.
I don't understand what original memory means. I think we're talking past each other tbh.
Quoted 6 lines
Quoted 1 line
This is a kexec problem (on x86 only) so let's fix it there.
Would you mind explaining what kexec needs to be done differently? Should it preserve the augmented memattr table independently if it is mapped in e820?
I don't know what 'mapped in e820' means.
Let's forget about what the memory attributes table actually contains, and just assume we can live without it, ok?
So when booting x86 via kexec (which is already detected in arch/x86/platform/efi/efi.c), the kernel should pretend that the table does not exist.
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
In reply to Ard BiesheuvelQuoted 29 lines · Ard Biesheuvel
Quoted 8 lines · Usama Arif
On 09/01/2025 16:15, Ard Biesheuvel wrote:
I think in the end whoevers' responsibility it is, the easiest path forward seems to be in kernel? (and not firmware or libstub)
Agreed. But as I pointed out in the other thread, the memory attributes table only augments the memory map with permission information, and can be disregarded, and given how badly we mangle the memory map on x86, maybe this is the right choice here.
Quoted 14 lines
Quoted 9 lines
Quoted 6 lines
The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service call option [3], [4], and
install_configuration_tabledoes not seem to work as a valid substitute.To do what, exactly?
To change the memory type from System RAM to either reserved or something more appropriate, i.e. any type that is not touched by kexec or any other userspace.
Quoted 7 lines
Quoted 5 lines
Basically the example code I attached at the end of the cover letter in
https://lore.kernel.org/all/[email protected]/
It could beEFI_ACPI_RECLAIM_MEMORYorEFI_RESERVED_TYPE, both of which aren't touched by kexec.This is a kexec problem (on x86 only) so let's fix it there.
I don't believe we can accurately tell if we are booting from a cold boot or kexec. There is bootloader_type available for x86, but not sure if we should rely on that. I think a way forward would be to move it behind a Kconfig option, something like below, which defaults to n for x86. Anyone who needs it can enable it. What do you think?
arch/x86/platform/efi/efi.c +2 -0
@@ -83,7 +83,9 @@ static const unsigned long * const efi_tables[] = { &efi_config_table, &efi.esrt, &prop_phys, +#ifdef CONFIG_EFI_MEMATTR &efi_mem_attr_table, +#endif #ifdef CONFIG_EFI_RCI2_TABLE &rci2_table_phys, #endif
drivers/firmware/efi/Kconfig +7 -0
@@ -287,6 +287,13 @@ config EFI_EMBEDDED_FIRMWARE bool select CRYPTO_LIB_SHA256 +config EFI_MEMATTR + bool "EFI Memory attributes table" + default n if X86_64 + help + EFI Memory Attributes table describes memory protections that may + be applied to the EFI Runtime code and data regions by the kernel. + endmenu config UEFI_CPER
drivers/firmware/efi/Makefile +3 -1
@@ -11,7 +11,9 @@ KASAN_SANITIZE_runtime-wrappers.o := n obj-$(CONFIG_ACPI_BGRT) += efi-bgrt.o -obj-$(CONFIG_EFI) += efi.o vars.o reboot.o memattr.o tpm.o +obj-$(CONFIG_EFI) += efi.o vars.o reboot.o tpm.o +obj-$(CONFIG_EFI_MEMATTR) += memattr.o + obj-$(CONFIG_EFI) += memmap.o ifneq ($(CONFIG_EFI_CAPSULE_LOADER),) obj-$(CONFIG_EFI) += capsule.o
drivers/firmware/efi/efi.c +2 -0
@@ -596,7 +596,9 @@ static const efi_config_table_type_t common_tables[] __initconst = { {SMBIOS_TABLE_GUID, &efi.smbios, "SMBIOS" }, {SMBIOS3_TABLE_GUID, &efi.smbios3, "SMBIOS 3.0" }, {EFI_SYSTEM_RESOURCE_TABLE_GUID, &efi.esrt, "ESRT" }, +#ifdef CONFIG_EFI_MEMATTR {EFI_MEMORY_ATTRIBUTES_TABLE_GUID, &efi_mem_attr_table, "MEMATTR" }, +#endif {LINUX_EFI_RANDOM_SEED_TABLE_GUID, &efi_rng_seed, "RNG" }, {LINUX_EFI_TPM_EVENT_LOG_GUID, &efi.tpm_log, "TPMEventLog" }, {EFI_TCG2_FINAL_EVENTS_TABLE_GUID, &efi.tpm_final_log, "TPMFinalLog" },
include/linux/efi.h +12 -0
@@ -783,9 +783,21 @@ extern unsigned long efi_mem_attr_table;*/ typedef int (*efi_memattr_perm_setter )(struct mm_struct *,efi_memory_desc_t *,bool ); +#ifdef CONFIG_EFI_MEMATTR extern int efi_memattr_init (void );extern int efi_memattr_apply_permissions (struct mm_struct *mm,efi_memattr_perm_setter fn); +#else +static inline int efi_memattr_init (void ) +{ +return 0 ; +} +static inline int efi_memattr_apply_permissions (struct mm_struct *mm, +efi_memattr_perm_setter fn) +{ +return 0 ; +} +#endif /* * efi_memdesc_ptr - get the n-th EFI memmap descriptor
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 38 lines · Usama Arif
Quoted 35 lines · Ard Biesheuvel
Quoted 8 lines · Usama Arif
On 09/01/2025 16:15, Ard Biesheuvel wrote:
I think in the end whoevers' responsibility it is, the easiest path forward seems to be in kernel? (and not firmware or libstub)
Agreed. But as I pointed out in the other thread, the memory attributes table only augments the memory map with permission information, and can be disregarded, and given how badly we mangle the memory map on x86, maybe this is the right choice here.
Quoted 19 lines
Quoted 9 lines
Quoted 6 lines
The next ideal place would be in libstub. However, it looks like InstallMemoryAttributesTable [2] is not available as a boot service call option [3], [4], and
install_configuration_tabledoes not seem to work as a valid substitute.To do what, exactly?
To change the memory type from System RAM to either reserved or something more appropriate, i.e. any type that is not touched by kexec or any other userspace.
Basically the example code I attached at the end of the cover letter in
https://lore.kernel.org/all/[email protected]/
It could beEFI_ACPI_RECLAIM_MEMORYorEFI_RESERVED_TYPE, both of which aren't touched by kexec.
Quoted 8 lines
Quoted 1 line
This is a kexec problem (on x86 only) so let's fix it there.
I don't believe we can accurately tell if we are booting from a cold boot or kexec. There is
bootloader_typeavailable for x86, but not sure if we should rely on that. I think a way forward would be to move it behind aKconfigoption, something like below, which defaults to n for x86. Anyone who needs it can enable it. What do you think?
Or we can do something like below?
drivers/firmware/efi/memattr.c +9 -0
@@ -24,6 +24,15 @@ int __init efi_memattr_init(void)efi_memory_attributes_table_t *tbl;unsigned long size; +#ifdef CONFIG_X86_64 +/* +* On x86_64, do not initialize memory attributes table +* if booting from kexec +*/ +if (bootloader_type >>4 ==0xd ) +return 0 ; +#endif +if (efi_mem_attr_table ==EFI_INVALID_TABLE_ADDR )return 0 ;
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
In reply to Usama ArifHi Usama,
Quoted 5 lines · Usama Arif
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.
Is the attr table BOOT SERVICE DATA? If so, does efi_mem_reserve() work for you?
Just refer to esrt.c.
Thanks
Dave
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 4 lines · Dave Young
Hi Usama,
Quoted 1 line · Usama Arif
Quoted 9 lines
Quoted 4 lines
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.Is the attr table BOOT SERVICE DATA? If so, does
efi_mem_reserve()work for you?
Just refer toesrt.c.
Hi Dave,
Its a bit difficult to reproduce the problem and therefore test the fix, but we are seeing it a lot in production. Ard proposed the same thing in
https://lore.kernel.org/all/[email protected]/
but as I mentioned there, I dont think that efi_mem_reserve would help, as efi_mem_reserve changes e820_table, while kexec looks at /sys/firmware/memmap which uses e820_table_firmware.
Thanks,
Usama
Quoted 3 lines
Thanks
Dave
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 18 lines · Usama Arif
Quoted 4 lines · Dave Young
Hi Usama,
Quoted 1 line · Usama Arif
Quoted 9 lines
Quoted 4 lines
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.Is the attr table BOOT SERVICE DATA? If so, does
efi_mem_reserve()work for you?
Just refer toesrt.c.
Quoted 8 lines
Hi Dave,
Its a bit difficult to reproduce the problem and therefore test the fix, but we are seeing it a lot in production. Ard proposed the same thing in
https://lore.kernel.org/all/[email protected]/
but as I mentioned there, I dont think thatefi_mem_reservewould help, asefi_mem_reservechangese820_table, while kexec looks at/sys/firmware/memmapwhich usese820_table_firmware.
I sent a question to pm people, if the sysfs memmap comes from e820_table then it will be fine. Let's see:
https://lore.kernel.org/all/CALu+AoS-nk4u=9UYP7BLS=diOxjJRf+vfv7KHXG=uXozoYazsw@mail.gmail.com/
Quoted 8 lines
Thanks,
UsamaQuoted 3 lines
Thanks
Dave
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 29 lines · Dave Young
Quoted 18 lines · Usama Arif
Quoted 4 lines · Dave Young
Hi Usama,
Quoted 1 line · Usama Arif
Quoted 9 lines
Quoted 4 lines
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.Is the attr table BOOT SERVICE DATA? If so, does
efi_mem_reserve()work for you?
Just refer toesrt.c.Quoted 8 lines
Hi Dave,
Its a bit difficult to reproduce the problem and therefore test the fix, but we are seeing it a lot in production. Ard proposed the same thing in
https://lore.kernel.org/all/[email protected]/
but as I mentioned there, I dont think thatefi_mem_reservewould help, asefi_mem_reservechangese820_table, while kexec looks at/sys/firmware/memmapwhich usese820_table_firmware.
Quoted 2 lines
I sent a question to pm people, if the sysfs memmap comes from
e820_tablethen it will be fine. Let's see:
s/e820_table/e820_table_kexec
Quoted 10 lines
https://lore.kernel.org/all/CALu+AoS-nk4u=9UYP7BLS=diOxjJRf+vfv7KHXG=uXozoYazsw@mail.gmail.com/
Quoted 8 lines
Thanks,
UsamaQuoted 3 lines
Thanks
Dave
Re: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Quoted 30 lines · Dave Young
Quoted 29 lines · Dave Young
Quoted 26 lines · Usama Arif
Quoted 4 lines · Dave Young
Hi Usama,
Quoted 1 line · Usama Arif
Quoted 9 lines
Quoted 4 lines
When this area is not reserved, it comes up as usable in
/sys/firmware/memmap. This means that kexec, which uses that memmap to find usable memory regions, can select the region whereefi_mem_attr_tableis and overwrite it andrelocate_kernel.Is the attr table BOOT SERVICE DATA? If so, does
efi_mem_reserve()work for you?
Just refer toesrt.c.Hi Dave,
Its a bit difficult to reproduce the problem and therefore test the fix, but we are seeing it a lot in production. Ard proposed the same thing in
https://lore.kernel.org/all/[email protected]/
but as I mentioned there, I dont think thatefi_mem_reservewould help, asefi_mem_reservechangese820_table, while kexec looks at/sys/firmware/memmapwhich usese820_table_firmware.
Quoted 4 lines
Quoted 2 lines
I sent a question to pm people, if the sysfs memmap comes from
e820_tablethen it will be fine. Let's see:s/e820_table/e820_table_kexec
Do you mean change /sys/firmware/memmap to point to e820_table_kexec instead of e820_table_firmware [1]?
I thought of doing this when the first bug was encountered last year, but didn't do it as I thought it would be frowned upon to change what sysfs file exposes to userspace.
[1] https://elixir.bootlin.com/linux/v6.12.6/source/arch/x86/kernel/e820.c#L31
Quoted 11 lines
Quoted 10 lines
https://lore.kernel.org/all/CALu+AoS-nk4u=9UYP7BLS=diOxjJRf+vfv7KHXG=uXozoYazsw@mail.gmail.com/
Quoted 8 lines
Thanks,
UsamaQuoted 3 lines
Thanks
Dave
kernel test robot
build botRe: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
In reply to Usama Arifkernel test robot noticed the following build errors:
Hi Usama,
[This is a private test report for your RFC patch.] kernel test robot noticed the following build errors:
[auto build test ERROR on efi/next]
[also build test ERROR on linus/master v6.13-rc6 next-20250109] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Usama-Arif/efi-memattr-Use-desc_size-instead-of-total-size-to-check-for-corruption/20250109-060158 base: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next patch link: https://lore.kernel.org/r/20250108215957.3437660-3-usamaarif642%40gmail.com patch subject: [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware config: i386-buildonly-randconfig-002-20250110 (https://download.01.org/0day-ci/archive/20250110/[email protected]/config) compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250110/[email protected]/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
All errors (new ones prefixed by >>):
In file included from arch/x86/platform/efi/efi.c:39:
In file included from include/linux/memblock.h:12:
In file included from include/linux/mm.h:2223:
include/linux/vmstat.h:504:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
504 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
505 | item];
| ~~~~
include/linux/vmstat.h:511:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
511 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
512 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
include/linux/vmstat.h:524:43: warning: arithmetic between different enumeration types ('enum zone_stat_item' and 'enum numa_stat_item') [-Wenum-enum-conversion]
524 | return vmstat_text[NR_VM_ZONE_STAT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~ ^
525 | NR_VM_NUMA_EVENT_ITEMS +
| ~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/platform/efi/efi.c:169:6: error: redefinition of 'arch_update_firmware_area' 169 | void arch_update_firmware_area(u64 addr, u64 size)
| ^
include/linux/efi.h:1360:27: note: previous definition is here
1360 | static inline void __init arch_update_firmware_area(u64 addr, u64 size)
| ^
4 warnings and 1 error generated.
vim +/arch_update_firmware_area +169 arch/x86/platform/efi/efi.c
167
168 /* Reserve firmware area if it was marked as RAM */
> 169 void arch_update_firmware_area(u64 addr, u64 size)
170 {
171 if (e820__get_entry_type(addr, addr + size) == E820_TYPE_RAM) {
172 e820__range_update_firmware(addr, size, E820_TYPE_RAM, E820_TYPE_RESERVED);
173 e820__update_table(e820_table_firmware);
174 }
175 }
176
Signature · 2 lines
0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki