linux-kernel - Re: ARM: relocation out of range (when loading a module)

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: <AANLkTimAFp7ORrJLw2d8-i5pK0MZGTyAN5kmRR37ky1v@mail.gmail.com>
Date:	Wed, 12 Jan 2011 10:05:19 -0600
From:	Dave Martin <dave.martin@...aro.org>
To:	Alexander Holler <holler@...oftware.de>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	Rabin Vincent <rabin@....in>, linux-kernel@...r.kernel.org,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Nicolas Pitre <nico@...xnic.net>
Subject: Re: ARM: relocation out of range (when loading a module)

On Tue, Jan 11, 2011 at 9:00 PM, Alexander Holler <holler@...oftware.de> wrote:
> Hello,

[...]

>                INIT_CALLS
>                CON_INITCALL
>                SECURITY_INITCALL
> +               /*
> +                * TODO: The size of INIT_RAM_FS could easily reach a
> +                * point (~16MB) when loading modules will fail because
> +                * relocations will be out of range. So this place here
> +                * isn't the best one.
> +                */
>                INIT_RAM_FS

In general, do we expect always to be able to avoid the situation
where branches in the kernel may need to cover too large a range ...
and is there any strategy for working aroung it?

If we have problems branching from the modules area into vmlinux, we
could possibly build modules with -fPIC : this would remove the
restriction on branch range, though there would also be some
performance impact for the modules...

Cheers
---Dave
--
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/