linux-kernel - Re: [RFC] arm: Update Booting document for FDT placement and reserved map

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] [day] [month] [year] [list]

Date:	Wed, 29 May 2013 20:05:09 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Grant Likely <grant.likely@...aro.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Russell King <linux@....linux.org.uk>,
	Catalin Marinas <catalin.marinas@....com>,
	Nicolas Pitre <nico@...aro.org>,
	Leif Lindholm <leif.lindholm@...aro.org>,
	Olivier Martin <olivier.martin@....com>,
	Marc Zyngier <marc.zyngier@....com>
Subject: Re: [RFC] arm: Update Booting document for FDT placement and reserved map

On Wed, May 29, 2013 at 3:55 PM, Grant Likely <grant.likely@...aro.org> wrote:

> In this patch I've stated that the initrd doesn't need to be included in
> the reserved map. However, should this be changed? Right now the
> decompressor doesn't actually look at the reserved map when
> decompressing and moving things around. If I'm reading the code
> correctly it is possible that the decompressor will overwrite the initrd
> if it gets placed too close to the kernel.

Maybe people aren't seeing this so much because anyone who
wants to place the ramfs close to the kernel (say because of
memory space constraints) is already using initramfs instead
of initrd?

Yours,
Linus Walleij
--
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/