On 30. 10. 24, 19:26, Gregory Price wrote:
you may also want to investigate this patch set: https://lore.kernel.org/all/20240913231954.20081-1-gourry@xxxxxxxxxx/ which I believe would have caught your "eat all memory" sign extention issue.
But it's memattr what is corrupted, not tpmeventlog. The reporter is using this for some time and it indeed works: --- a/drivers/firmware/efi/memattr.c +++ b/drivers/firmware/efi/memattr.c @@ -12,7 +12,7 @@ #include <asm/early_ioremap.h> -static int __initdata tbl_size; +static phys_addr_t __initdata tbl_size; unsigned long __ro_after_init efi_mem_attr_table = EFI_INVALID_TABLE_ADDR; /* -- js suse labs
