public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vernon Mauery <vernux@us.ibm.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: "Antti Halonen" <antti.halonen@secgo.com>,
	"linux-os (Dick Johnson)" <linux-os@analogic.com>,
	"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: searching exported symbols from modules
Date: Fri, 21 Apr 2006 07:03:07 -0700	[thread overview]
Message-ID: <200604210703.07856.vernux@us.ibm.com> (raw)
In-Reply-To: <14930.1145604787@kao2.melbourne.sgi.com>

On Friday 21 April 2006 00:33, Keith Owens wrote:
> "Antti Halonen" (on Wed, 19 Apr 2006 16:08:37 +0300) wrote:
> >Hi Dick,
> >
> >Thanks for your response.
> >
> >> `insmod` (or modprobe) does all this automatically. Anything that's
> >> 'extern' will get resolved. You don't do anything special. You can
> >> also use `depmod` to verify that you won't have any problems loading.
> >> `man depmod`.
> >
> >Yes, I know insmod and herein the problem lies. I have a module where
> >I want to use functions provided by another module, _if_ it is present,
> >otherwise use modules internal functions.
>
> symbol_get() and symbol_put().  See include/linux/module.h.  If
> symbol_get() returns NULL then the symbol does not exist.

The trick with symbol_get is that it is marked as EXPORT_SYMBOL_GPL, so only 
GPL modules can use it.  Not that that is a bad thing though. :)

If you want all of these nice kernel features, GPL your module!

--Vernon

  reply	other threads:[~2006-04-21 14:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 13:08 searching exported symbols from modules Antti Halonen
2006-04-19 14:55 ` linux-os (Dick Johnson)
2006-04-19 15:53 ` Robin Holt
2006-04-21  7:33 ` Keith Owens
2006-04-21 14:03   ` Vernon Mauery [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-20  7:15 Antti Halonen
2006-04-20  8:01 ` Kyle Moffett
2006-04-20 17:00 ` Adrian Bunk
2006-04-20  6:12 Antti Halonen
2006-04-20  7:00 ` Kyle Moffett
2006-04-20  5:50 Antti Halonen
2006-04-20  5:59 ` James Morris
2006-04-19 15:59 Antti Halonen
2006-04-19 16:02 ` Arjan van de Ven
2006-04-19 15:34 Antti Halonen
2006-04-19 15:43 ` Arjan van de Ven
2006-04-19 14:54 Antti Halonen
2006-04-19 15:17 ` Arjan van de Ven
2006-04-19 12:44 Antti Halonen
2006-04-19 12:59 ` linux-os (Dick Johnson)
2006-04-19 14:55   ` Jim Cromie
2006-04-19 14:22 ` Arjan van de Ven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200604210703.07856.vernux@us.ibm.com \
    --to=vernux@us.ibm.com \
    --cc=antti.halonen@secgo.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox