From: John Sigler <linux.kernel@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Dumping the checksums in a module
Date: Fri, 18 May 2007 17:02:49 +0200 [thread overview]
Message-ID: <464DC019.6010008@free.fr> (raw)
Hello everyone,
I'm getting "disagrees about version of symbol struct_module" messages,
and I'm trying to understand why.
As far as I understand (which is not very far), if I define
CONFIG_MODVERSIONS, then checksums for various functions (all exported
functions?) and various structures (which ones?) will be included inside
the kernel image, and written to Module.symvers. When an out-of-tree
module is built, it will also include these checksums.
How do I list the checksums within a module?
$ /sbin/modinfo -V
module-init-tools version 3.2.2
$ uname -a
Linux venus 2.6.18.6 #1 PREEMPT Thu Feb 8 18:04:49 CET 2007 i686
pentium4 i386 GNU/Linux
$ /sbin/modinfo test.ko
filename: test.ko
vermagic: 2.6.20.7-rt8 preempt mod_unload PENTIUMIII REGPARM
depends:
parm: pConfig_file:charp
parm: allocator_himem:An integer (int)
parm: EnableIdleMode:An integer (int)
parm: Board_ID:An integer (int)
parm: Diagnostic:An integer (int)
$ hexdump -C test.ko | grep -A2 struct_
000752e0 17 98 07 0e 73 74 72 75 63 74 5f 6d 6f 64 75 6c
|....struct_modul|
000752f0 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|e...............|
00075300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
I think this means that, in this module, the checksum for symbol
struct_module is 0x1798070e, right?
Is there a simpler way to list all the checksums?
Regards.
next reply other threads:[~2007-05-18 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 15:02 John Sigler [this message]
2007-05-18 20:27 ` Dumping the checksums in a module Jan Engelhardt
2007-05-18 20:46 ` Sam Ravnborg
2007-05-22 8:19 ` John Sigler
2007-05-22 8:13 ` John Sigler
2007-05-22 19:53 ` Jan Engelhardt
2007-05-23 15:18 ` John Sigler
-- strict thread matches above, loose matches on Subject: below --
2007-06-19 11:59 John Sigler
2007-06-19 13:18 ` Arjan van de Ven
2007-06-19 14:40 ` John Sigler
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=464DC019.6010008@free.fr \
--to=linux.kernel@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.