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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 9 Jan 2016 01:13:46 +0900
From:	Masahiro Yamada <yamada.masahiro@...ionext.com>
To:	"Jon Medhurst (Tixy)" <tixy@...aro.org>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Russell King - ARM Linux <linux@....linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [Question] Any restriction for the location of initramdisk?

Hi Jon,

2016-01-08 19:22 GMT+09:00 Jon Medhurst (Tixy) <tixy@...aro.org>:
> 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.


Uh, the document states that clearly.

Thanks!




-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ