From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: John Sigler <linux.kernel@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: Dumping the checksums in a module
Date: Fri, 18 May 2007 22:46:50 +0200 [thread overview]
Message-ID: <20070518204650.GA17343@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0705182225450.9015@yvahk01.tjqt.qr>
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"
Sam
next prev parent reply other threads:[~2007-05-18 20:46 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 [this message]
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=20070518204650.GA17343@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.kernel@free.fr \
/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