From: Kyle Moffett <mrmacman_g4@mac.com>
To: omkar lagu <omkarlagu@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to call a function in a module from the kernel code !!! (Linux kernel)
Date: Thu, 9 Feb 2006 18:07:32 -0500 [thread overview]
Message-ID: <383FCBAC-AB8E-4DFA-8716-D7BBF6409FDA@mac.com> (raw)
In-Reply-To: <20060209192510.32377.qmail@web50307.mail.yahoo.com>
On Feb 09, 2006, at 14:25, omkar lagu wrote:
> hello sir,
>
> we wanted to call a function in our module ll from shm.c file
> (which is in the kernel)
>
> so we declared function pointer in shm.c
> unsigned long long (*ptr1)(int)
>
> we declared it as extern in shm.h
> extern unsigned long long (*ptr1)(int)
>
> then we declared also in our module (ll)
> extern unsigned long long (*ptr1)(int)
>
> we initialized it to ptr1 = commun; in init module of ll.c where
> commun is we wanted to call from the kernel
>
> but it gave an error as undefined refernce to ptr1 when we inserted
> our module..
>
> can you help on this thing or can you give us a example regarding
> how it is done ??
It would help a lot if you could post a link to your source code.
Let me point out (in case you don't know this already) that if you do
what you describe and distribute the result, you are automatically
licensing your ll.c file under the GPLv2. By distributing a
derivative of both the Linux kernel and your proprietary module (You
are taking Linux kernel sources and modifying them explicitly for
your module), the result must be GPL. Also, I think what you are
describing is basically impossible. I believe what you want to do is
this:
/* in shm.c */
unsigned long long (*ptr1)(int);
EXPORT_SYMBOL(ptr1);
However this makes it impossible to reliably remove your module,
because a process could race entering the function as the module
loader is trying to remove the module.
Cheers,
Kyle Moffett
--
There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the
other way is to make it so complicated that there are no obvious
deficiencies. The first method is far more difficult.
-- C.A.R. Hoare
next prev parent reply other threads:[~2006-02-09 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 19:25 Fwd: " omkar lagu
2006-02-09 19:32 ` Michael Buesch
2006-02-09 23:07 ` Kyle Moffett [this message]
2006-02-10 7:55 ` Steven Rostedt
2006-02-10 8:16 ` Kyle Moffett
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=383FCBAC-AB8E-4DFA-8716-D7BBF6409FDA@mac.com \
--to=mrmacman_g4@mac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omkarlagu@yahoo.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
all inboxes | Powered by JetHome®