linux-kernel - Re: How to link a .o with all modules

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]

Message-ID: <20080508202200.GA12578@uranus.ravnborg.org>
Date:	Thu, 8 May 2008 22:22:00 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Kumar Gala <galak@...nel.crashing.org>
Cc:	lkml List <linux-kernel@...r.kernel.org>,
	"linuxppc-dev@...abs.org list" <linuxppc-dev@...abs.org>
Subject: Re: How to link a .o with all modules

On Thu, May 08, 2008 at 09:16:10AM -0500, Kumar Gala wrote:
> 
> On May 5, 2008, at 3:44 PM, Sam Ravnborg wrote:
> 
> >>>
> >>>
> >>>Let me know if this does address your question.
> >>
> >>The problem is MODPOST complains about undefined symbols:
> >>
> >> MODPOST 24 modules
> >>ERROR: "_restgpr_20_x" [net/key/af_key.ko] undefined!
> >>ERROR: "_restgpr_25_x" [net/key/af_key.ko] undefined!
> >>ERROR: "_restgpr_30_x" [net/key/af_key.ko] undefined!
> >
> >I need a bit more context to try to analyse this.
> >Where did you expect _restgpr_20_x to be defined.
> >If in vmlinux then were they present in the
> >Module.symvers file?
> 
> No they aren't there since we I'm not EXPORT_SYMBOL() them.  Should I  
> also be doing EXPORT_SYMBOL?

So modpost claim it cannot find the symbols.

> 
> >If in the linked in .o file - could you
> >see the symbols using objdump.
> 
> Yes.
> 
> readelf -a:
> 
> ...
> Symbol table '.symtab' contains 113 entries:
>    Num:    Value  Size Type    Bind   Vis      Ndx Name
> ...
>      5: 00000000     0 FUNC    GLOBAL DEFAULT    1 _savegpr_14
>      6: 00000000     0 FUNC    GLOBAL DEFAULT    1 _save32gpr_14
> ...

Strange.

I did not look closer.
But it looks like the linker failed to resolve these symbols
in the final link somehow - despite the symbols are present in
the linked in .o file.

Can you try to drop me the output of the relocation records for the
finally linked .o file (the one with your .o file linked in).

objdump -r IIRC

	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/