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, 17 Mar 2010 02:13:53 -0700
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	Will L Givens <wlgivens@...il.com>
CC:	'Michael Cree' <mcree@...on.net.nz>,
	'Raúl Porcel' 
	<armin76@...too.org>, 'Matt Turner' <mattst88@...il.com>,
	linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org
Subject: Re: Will's kernel compilation error

On 03/17/2010 01:55 AM, Will L Givens wrote:
>
>
>> -----Original Message-----
>> From: Michael Cree [mailto:mcree@...on.net.nz]
>> Sent: Wednesday, March 17, 2010 02:34
>> To: Raúl Porcel
>> Cc: Matt Turner; Will L Givens; 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.
>
> Well a monolithic kernel, which mine isn't, actually runs faster than a
> modular one despite being larger... that's been proven several times over
> the years. In the past I used to roll monolithic kernels simply for
> emergency boot situations and because kernel modules were notorious for not
> compiling properly with all kinds of undefined symbols... rolling them into
> the kernel was a quick fix. Do you honestly believe all those different
> modules, written by a slew of different people, will build properly let
> alone function properly? Kernel-2.6.34-rc1 is the FIRST one that I've seen
> where the netfilter modules all compiled!
>
> Another thing, some components 'have' to be built into the kernel because
> they won't automatically load or the kernel config makes it mandatory. The
> auto load function of past kernels has been pretty iffy at best and granted
> I've yet to actually load this release, I do have my doubts. So important
> things such as my aic7xxx drivers, ali drivers, 751 chipset, etc. I roll
> into the kernel itself.
>
> The things that you've stated I can understand but on when you get right
> down to it, it's not a major issue. My 'monolithic' kernel is only 1.9MB @
> 89MB/s. Personally I feel they should make small-data an patch addon, it
> would save a lot of people a some grief. Some ppl will select them (modules)
> either intentionally or by accident and the majority of folks are not
> running AT HDD's on a flaky IDE controller. Sincerely Will L G
>
> PS Whatever you guys decide please make it obvious... the aboot/kernel
> change a few years ago, caused a lot of Alpha Linux users to bug out...
> About the only ppl aware of the change was Ivan and a handful of Debian
> folks.
>
>
> --
> 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/
>
can you bisect this?

Justin P.Mattock
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ