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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Jun 2010 21:35:30 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Vladislav Bolkhovitin <vst@...b.net>
Cc:	David Miller <davem@...emloft.net>, 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

On Tue, Jun 22, 2010 at 11:07:51PM +0400, Vladislav Bolkhovitin wrote:
>
> David Miller, on 06/17/2010 12:35 AM wrote:
>> From: Vladislav Bolkhovitin <vst@...b.net>
>>
>> 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.
>>
> 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.

They should all be there automagically.
A few things to try out...
What machine is this being build on?

Your Makefile contains this:
> ifeq ($(KVER),)
>   ifeq ($(KDIR),)
>     KVER = $(shell uname -r)
>     KDIR := /lib/modules/$(KVER)/build
>   endif
> else
>   KDIR := /lib/modules/$(KVER)/build
> endif
> 

But does /lib/modules/... contain a sparc kernel?

You could try to build your module using: V=1

And reply with the output. This should give a clue about what flags are picked
up from where.

Most of your Makefile looks fine - I guess we need to find the bug
in the build environmnet and not in the Makefile.

	Sam
--
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/