Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755535Ab1BKJp4 (ORCPT ); Fri, 11 Feb 2011 04:45:56 -0500 Received: from mail-wy0-f174.google.com ([74.125.82.174]:60878 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755130Ab1BKJpz convert rfc822-to-8bit (ORCPT ); Fri, 11 Feb 2011 04:45:55 -0500 MIME-Version: 1.0 In-Reply-To: <20110211093853.GA23404@n2100.arm.linux.org.uk> References: <4D2D1942.4050905@ahsoftware.de> <20110112184258.GH11039@n2100.arm.linux.org.uk> <20110210154322.GE1742@n2100.arm.linux.org.uk> <20110211093853.GA23404@n2100.arm.linux.org.uk> Date: Fri, 11 Feb 2011 09:45:53 +0000 Message-ID: Subject: Re: ARM: relocation out of range (when loading a module) From: Dave Martin To: Russell King - ARM Linux Cc: Nicolas Pitre , Sachin Verma , Rabin Vincent , Alexander Holler , lkml , linux-arm-kernel , catalin.marinas@arm.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1495 Lines: 31 On Fri, Feb 11, 2011 at 9:38 AM, Russell King - ARM Linux wrote: > On Fri, Feb 11, 2011 at 09:31:04AM +0000, Dave Martin wrote: >> You could probably cook up a good upper bound based on the size of the >> kernel and the number of symbols in the module: i.e., assume that >> every undefined symbol in the module needs to be fixed up to point at >> the most distant symbol in the kernel. >> >> For people with normal-sized kernels, this bound will probably work >> out as zero most of the time (i.e., the current situation). ?For >> people with big kernels, or when many modules are already loaded, it >> may work out at 100% -- but that's the price to pay for guaranteed >> preallocation of the space required for the veneers. ?And anyway, you >> may really need a substantial chunk of those veneers in such cases. > > I think it's going to be easier just to re-order the kernel image link > order to solve that problem. ?That just leaves uclinux... > But if the kernel is big, or there are many modules, changing the order can't solve the problem surely? Or is the problem purely caused by having the initramfs in the way, and we think the amount of actual code will never be big enough to cause a problem? Cheers ---Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/