linux-kernel - Re: Kernel module unable to find an exported symbol

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] [day] [month] [year] [list]

Message-ID: <740b8bba0804131458w7a4f22bco3f4e5c48b75169c6@mail.gmail.com>
Date:	Sun, 13 Apr 2008 14:58:26 -0700
From:	"David Erickson" <halcyon1981@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	"Dmitri Vorobiev" <dmitri.vorobiev@...il.com>
Subject: Re: Kernel module unable to find an exported symbol

On Sun, Apr 13, 2008 at 2:52 PM, Dmitri Vorobiev
<dmitri.vorobiev@...il.com> wrote:
> David Erickson пишет:
>
> > Hi everyone, I have two kernel modules I am developing, both use the
>  > call_rcu exported function. The core module finds it no problem,
>  > installs, and uses it.  The second module however when I try to insmod
>  > it complains:
>  >
>  > Unknown symbol call_rcu
>  >
>  > I have verified that it is exported via /proc/kallsyms:
>  > c04348c8 T call_rcu
>  >
>  > I am at a loss as to how to proceed, can anyone shed some light on how
>  > this could be happening? Or how to diagnose and debug the problem?
>
>  It is very much possible that adding the following line to the source
>  code of your module will help:
>
>  MODULE_LICENSE("GPL");
>
>  HTH,
>  Dmitri

That did the trick, thank you Dmitri!

-David