From: "V. Guruprasad" <prasad@watson.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: difficulty with symbol export
Date: Mon, 29 Apr 2002 08:35:14 -0400 [thread overview]
Message-ID: <20020429083514.A21779@watson.ibm.com> (raw)
Hi all,
Just playing with the kernel code, I added a silly function
struct file_operations *get_socket_fileops ()
{
return &socket_file_ops;
}
at the bottom of net/socket.c, and
EXPORT_SYMBOL(get_socket_fileops);
into net/netsyms.c, expecting to be able to call this function
from a loadable module and to printk the function addresses
from the file_operations struct.
However, on rebooting into this modified kernel, my test module
fails to load, saying
foo.o: unresolved symbol get_socket_fileops
even though the symbol looks exported in vmlinux (nm) and
in /boot/System.map:
c020ca90 T get_socket_fileops
0c2b52bf ? __kstrtab_get_socket_fileops
0c2ba358 ? __ksymtab_get_socket_fileops
which looks exactly like sock_create, which the module *is*
able to address.
Any pointers?
thanks,
-prasad.
------------------------
V. Guruprasad ('prasad'),
http://www.columbia.edu/~vg96
next reply other threads:[~2002-04-29 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 12:35 V. Guruprasad [this message]
2002-04-29 14:55 ` difficulty with symbol export Kai Germaschewski
2002-04-29 15:14 ` V. Guruprasad
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=20020429083514.A21779@watson.ibm.com \
--to=prasad@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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