linux-kernel - Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor load address

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: <CAL1qeaHSErgc=W4mGhDAm7cu_J4wrOik27joB0Rd-2P7dk=QuA@mail.gmail.com>
Date:	Tue, 24 Feb 2015 13:39:03 -0800
From:	Andrew Bresticker <abrestic@...omium.org>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Ralf Baechle <ralf@...ux-mips.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linux-MIPS <linux-mips@...ux-mips.org>,
	Ezequiel Garcia <ezequiel.garcia@...tec.com>,
	James Hartley <james.hartley@...tec.com>,
	James Hogan <james.hogan@...tec.com>,
	Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH 2/5] MIPS: Allow platforms to specify the decompressor
 load address

On Tue, Feb 24, 2015 at 12:15 AM, Arnd Bergmann <arnd@...db.de> wrote:
> On Monday 23 February 2015 17:31:44 Andrew Bresticker wrote:
>> Platforms which use raw zboot images may need to link the image at
>> a fixed address if there is no other way to communicate the load
>> address to the bootloader.  Allow the per-platform Kbuild files
>> to specify an optional zboot image load address (zload-y) and fall
>> back to calc_vmlinuz_load_addr if unset.
>>
>> Signed-off-by: Andrew Bresticker <abrestic@...omium.org>
>> Cc: Lars-Peter Clausen <lars@...afoo.de>
>
> No objections to the patch, but have you considered doing the
> same thing as ARM's AUTO_ZRELADDR, where we calculate the
> address at runtime from the entry point?
>
> I assume this is the same kind of address you are talking
> about here; if not, nevermind.

It is the same sort of issue, though I think the only way to solve it
on MIPS would be to copy the image to the address it was linked at,
which could be problematic if there's overlap.  There's also the cache
maintenance we'd have to do, which varies from CPU to CPU (and more so
the ARM I believe).
--
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/