linux-kernel - Re: [Question] Any restriction for the location of initramdisk?

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]

Date:	Fri, 08 Jan 2016 10:22:24 +0000
From:	"Jon Medhurst (Tixy)" <tixy@...aro.org>
To:	Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [Question] Any restriction for the location of initramdisk?

On Fri, 2016-01-08 at 16:16 +0900, Masahiro Yamada wrote:
> Hi.
> 
> 
> I know DTB should be located within the reach of the kernel
> so that the kernel can get access to it at the early boot stage.
> In other words, DTB should be put in the low memory area.
> 
> Does initramdisk has the similar restriction?

I assume so, as that's what Documentation/arm/Booting says ...

5. Load initramfs.
------------------

Existing boot loaders:		OPTIONAL
New boot loaders:		OPTIONAL

If an initramfs is in use then, as with the dtb, it must be placed in
a region of memory where the kernel decompressor will not overwrite it
while also with the region which will be covered by the kernel's
low-memory mapping.

A safe location is just above the device tree blob which itself will
be loaded just above the 128MiB boundary from the start of RAM as
recommended above.

-- 
Tixy