linux-kernel - Re: [PATCH] x86, efi: Only print warning when desc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DB850D1.30203@kernel.org>
Date:	Wed, 27 Apr 2011 10:22:25 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Matt Fleming <matt@...sole-pimps.org>
CC:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>,
	Huang Ying <ying.huang@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86, efi: Only print warning when desc_size is smaller
 than defined one.

On 04/27/2011 04:39 AM, Matt Fleming wrote:
> On Tue, 26 Apr 2011 15:42:24 -0700
> Yinghai Lu <yinghai@...nel.org> wrote:
> 
>>
>> One system get warning:
>> 	Kernel-defined memdesc doesn't match the one from EFI!
>>
>> UEFI spec allows GetMemoryMap() return bigger desc_size and desc_ver for future
>> extension.
>> And desc_size is already used to get offset of next memory entry.
>>
>> Only need to check if desc_size is smaller than defined struct.
>>
>> Also print the size in warning if it happens.
>>
>> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>>
>> ---
>>  arch/x86/platform/efi/efi.c |    5 +++--
>>  1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> Index: linux-2.6/arch/x86/platform/efi/efi.c
>> ===================================================================
>> --- linux-2.6.orig/arch/x86/platform/efi/efi.c
>> +++ linux-2.6/arch/x86/platform/efi/efi.c
>> @@ -448,9 +448,10 @@ void __init efi_init(void)
>>  		printk(KERN_ERR "Could not map the EFI memory map!\n");
>>  	memmap.map_end = memmap.map + (memmap.nr_map * memmap.desc_size);
>>  
>> -	if (memmap.desc_size != sizeof(efi_memory_desc_t))
>> +	if (memmap.desc_size < sizeof(efi_memory_desc_t))
>>  		printk(KERN_WARNING
>> -		  "Kernel-defined memdesc doesn't match the one from EFI!\n");
>> +		  "Kernel-defined memdesc size is bigger than the one from EFI! %ld > %ld\n",
>> +			 sizeof(efi_memory_desc_t), memmap.desc_size);
> 
> Does it make sense for this to just be a warning? If
> sizeof(efi_memory_desec_t) > sizeof(memmap.desc_size) aren't we going
> to run into some pretty serious problems when we start accessing
> memory descriptors?
> 
> Would it not make more sense for this to be a BUG_ON()? In the unlikely
> event that the kernel's efi_memory_desc_t is too large I really don't
> see how we can recover from that.

Using WARNING is ok here.

1. bootloader aka grub.efi will convert efi memmap to e820 memmap and pass it in boot params.
   and current grub.efi does not compare desc_size and struct size.
2. kernel efi.c will only need to use desc_size when
   a. do_add_efi_memmap when "add_efi_memmap" is appended. it will add more entries in case bootloader miss some.
   b. for print_efi_memmap() debug purpose.

So if that efi_memmap is broken, those code can not be reached.

other case: if efi_memmap is broken or bootloader does not convert it properly. user could specify mem= or memmap= to pass info to boot.
if they can boot, print_efi_memmap could print out the messed up memmap for them.
if you change to BUG_ON, they can not boot anymore.

Thanks

Yinghai Lu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/