linux-kernel - Re: Will's kernel compilation error

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]

Date:	Wed, 17 Mar 2010 20:34:06 +1300
From:	Michael Cree <mcree@...on.net.nz>
To:	Raúl Porcel <armin76@...too.org>
CC:	Matt Turner <mattst88@...il.com>,
	Will L Givens <wlgivens@...il.com>,
	linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org
Subject: Re: Will's kernel compilation error

On 17/03/10 08:34, Raúl Porcel wrote:
> Have one.
>
> My error is as follows:
>
> net/built-in.o: In function `svc_auth_unregister':
> (.text+0xb822c): relocation truncated to fit: GPREL16 against `.sbss'

Right, I've confirmed that with the supplied config.  What's happening 
is that the small data area (where certain static data are stored) has 
exceeded 64kB which is the limit under the small data model.  As noted 
elsewhere on this thread it can be solved by compiling with the large 
data model, but that incurs extra CPU instructions whenever the data 
area is accessed.

A better solution, in my view, is to concert some drivers to modules.  I 
note that the config has a large number of devices to be built (some of 
which are denoted as having been tested on x86/x86_64/ia64 only).  I 
converted a few drivers, and most of the selected filesystems (do you 
really need them all at boot time?) into modules.  The kernel then 
builds correctly.

But if people insist on being able to build impractical monolithic 
kernels on Alpha I will post my patch to add a kernel option for the 
large data model.

Cheers
Michael.
--
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/