linux-kernel - Re: Error "Unknown relocation: 36" on module load on Sparc

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:	Tue, 22 Jun 2010 23:07:51 +0400
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	David Miller <davem@...emloft.net>
CC:	sparclinux@...r.kernel.org, simone.ricci@...il.com,
	scst-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	Nick.Couchman@...kr.com, Michal Marek <mmarek@...e.cz>,
	linux-kbuild@...r.kernel.org
Subject: Re: Error "Unknown relocation: 36" on module load on Sparc


David Miller, on 06/17/2010 12:35 AM wrote:
> From: Vladislav Bolkhovitin <vst@...b.net>
> Date: Wed, 16 Jun 2010 23:05:41 +0400
> 
>> We in SCST project have a very strange problem on Sparc. Our main
>> module scst.ko, if built as a module out of the kernel tree, can't be
>> loaded and "modprobe scst" returns:
>>
>> FATAL: Error inserting scst
>> (/lib/modules/2.6.26-2-sparc64/extra/scst.ko): Invalid module format
>>
>> The following message is immediately spit out by the kernel:
>> [ 1686.676534] module scst: Unknown relocation: 36
> 
> You're building the module with incorrect compiler flags, in
> particular somehow the "-mcmodel=medlow" option is not getting passed
> into the module build and thus the wrong code model is being used to
> build the module.
> 
> There are a host of other sparc64 specific compiler options that must
> be present for a correct build as well.  The only way to get it done
> correctly is to properly inherit the option settings made by
> arch/sparc/Makefile and friends in the kernel tree.

Thank you. This gives us the direction away from the current dead end. 
We will make the needed changes in our Makefiles.

But we surprised that such platform specific compiler flags have to be 
manually maintained by out of the kernel tree modules developers. We 
thought kbuild environment doing it automatically. Particularly, 
Documentation/kbuild/modules.txt doesn't say anything about manual 
platform specific flags.

I added kbuild developers on CC and attached again our Makefile just in 
case if they would like to look at it.

Thanks,
Vlad

View attachment "Makefile" of type "text/plain" (3902 bytes)