Do you know the bug of EXPORT_SYMBOL()
tal.shorer at gmail.com
Fri Jul 24 10:20:42 EDT 2015
With in-tree modules, the compilation process can determine
dependencies and that's why modprobe works with them (insmod doesn't).
How do you want the kernel to know where the symbol comes from? Why
load your mod1 and not my mod3 that also defines myfunc()? Who's going
to call init_module on your mod1? Where in the filesystem should it
look for it?
On Fri, Jul 24, 2015 at 3:40 PM, Navy <navych at 126.com> wrote:
> On Fri, Jul 24, 2015 at 01:48:57PM +0530, Pranay Srivastava wrote:
>> On Fri, Jul 24, 2015 at 11:19 AM, Navy <navych at 126.com> wrote:
>> > Hi
>> > To my understanding, EXPORT_SYMBOL() is used to export a symbol in
>> > Why this bug is not be fixed?
>> It's a long way from 2.6 now. can you send something about this "bug"?
> Hi Pranay,
> The detail is below:
> Maybe other people think out-of-tree modules should not be supported.
> I don't know How do the in-tree modules reference other symbols and be insmod
> without this problem. If you can help me about this, I will deeply grateful.
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
More information about the Kernelnewbies