linux-kernel - Re: Problems using EXPORT_SYMBOL with lib/flex

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:	Wed, 1 Dec 2010 13:20:30 +0000
From:	Alex Bennee <kernel-hacker@...nee.com>
To:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Problems using EXPORT_SYMBOL with lib/flex_array

On 1 December 2010 12:05, Alex Bennee <kernel-hacker@...nee.com> wrote:
> Hi,
>
> I want to be able to use the flex_array functions in my module so I
> wanted to EXPORT_SYMBOL the API.
> <snip>
> Am I being a
> little dim or is there some other magic foo that needs doing to add an
> export to a library function?

It turns out for library code there is. If the .o is only included in
the lib-y section then it will never get scanned for exported kernel
symbols. Tweaking the lib/Makefile so obj-y included flex_array.o did
the trick.

I'm unsure if this behaviour is what is wanted?

-- 
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk
--
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/