linux-kernel - Re: [PATCH v3 06/10] arm64: efi: add EFI stub

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: <E4BDBC23-A96A-4D84-B7EE-B7967D4E4DDD@linaro.org>
Date:   Wed, 8 Feb 2017 16:29:50 +0000
From:   Ard Biesheuvel <ard.biesheuvel@...aro.org>
To:     Timur Tabi <timur@...eaurora.org>
Cc:     Leif Lindholm <leif.lindholm@...aro.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>, linux-efi@...r.kernel.org,
        lkml <linux-kernel@...r.kernel.org>,
        Mark Salter <msalter@...hat.com>,
        Catalin Marinas <catalin.marinas@....com>,
        Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH v3 06/10] arm64: efi: add EFI stub



> On 8 Feb 2017, at 16:28, Timur Tabi <timur@...eaurora.org> wrote:
> 
>> On Fri, Apr 4, 2014 at 1:45 PM, Leif Lindholm <leif.lindholm@...aro.org> wrote:
>> 
>> +/*
>> + * EFI entry point for the arm/arm64 EFI stubs.  This is the entrypoint
>> + * that is described in the PE/COFF header.  Most of the code is the same
>> + * for both archictectures, with the arch-specific code provided in the
>> + * handle_kernel_image() function.
>> + */
>> +unsigned long __init efi_entry(void *handle, efi_system_table_t *sys_table,
>> +                              unsigned long *image_addr)
>> +{
> 
> ...
> 
>> +
>> +       status = handle_cmdline_files(sys_table, image, cmdline_ptr,
>> +                                     "initrd=", dram_base + SZ_512M,
>> +                                     (unsigned long *)&initrd_addr,
>> +                                     (unsigned long *)&initrd_size);
> 
> So I know this patch is almost three years old, but why is there a
> 512M limit on the initrd size?
> 

How do you reckon this constitutes a limit?

> -- 
> Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project.