public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Sigler <linux.kernel@free.fr>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dumping the checksums in a module
Date: Tue, 22 May 2007 10:19:07 +0200	[thread overview]
Message-ID: <4652A77B.6020306@free.fr> (raw)
In-Reply-To: <20070518204650.GA17343@uranus.ravnborg.org>

Sam Ravnborg wrote:
> On Fri, May 18, 2007 at 10:27:06PM +0200, Jan Engelhardt wrote:
>> On May 18 2007 17:02, John Sigler wrote:
>>> 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?
>>>
>>> Is there a simpler way to list all the checksums?
>> 22:25 ichi:~ > modinfo aes
>> srcversion:     8CB82B3A254D5A950FD0D14
>>
>> I think this one checksum is computed out of all functions that
>> the module uses.
>
> It is computed based on all files used for the module.
> Check help for "Loadable module support | Source Checksum for all modules"

How do I list *all* the checksums inside a given module?

For example, I want to know the checksum for "struct_module" in test.ko

$ grep struct_module Module.symvers
0x71d1e11f      struct_module   vmlinux EXPORT_SYMBOL

That's for the kernel.

$(MAGIC_COMMAND_TO_DUMP_CHECKSUMS) test.ko | grep struct_module
=> ...

Regards.

  reply	other threads:[~2007-05-22  8:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 15:02 Dumping the checksums in a module John Sigler
2007-05-18 20:27 ` Jan Engelhardt
2007-05-18 20:46   ` Sam Ravnborg
2007-05-22  8:19     ` John Sigler [this message]
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=4652A77B.6020306@free.fr \
    --to=linux.kernel@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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