linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shakthi Kannan <shakthimaan@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CRC calculation in Module.symvers
Date: Fri, 9 Sep 2011 10:20:04 +0530	[thread overview]
Message-ID: <CABG-yt030LAdqbRySzs8sj0Ajwst_c8RHf7yOyG9Eihh6mmf+w@mail.gmail.com> (raw)
In-Reply-To: <4E67699E.80208@suse.cz>

Hi Michal,

--- On Wed, Sep 7, 2011 at 6:24 PM, Michal Marek <mmarek@suse.cz> wrote:
| You need at least -include include/generated/autoconf.h
\--

I tried using:

$  gcc -E -D__GENKSYMS__ -DCONFIG_MODVERSIONS -DEXPORT_SYMTAB
crypto/api.c -I/tmp/linux-3.0.2/include
-I/tmp/linux-3.0.2/arch/x86/include -include
include/generated/autoconf.h  | ./scripts/genksyms/genksyms

and it returned the checksums like:

  __crc_crypto_alg_list = 0x86fb488e ;
  __crc_crypto_alg_sem = 0xb7865a4f ;
  __crc_crypto_chain = 0x2f947450 ;
  __crc_crypto_mod_get = 0x67cda209 ;
  ...

But, in Module.symvers there is only crypto_mod_get and its checksum
is 0x3286637f which is different from the one listed above.

---
| $ make V=1 crypto/api.symtypes
|
| this will generate a file with the symbol expansions.
\--

This generated the api.symtypes file.

---
| And if you copy
| the commandline without the >/dev/null redirection, you'll see the
| calculated checksums on standard output.
\--

Sorry, I didn't understand. Can you elaborate on what needs to be done here?

Thanks for your reply,

SK

-- 
Shakthi Kannan
http://www.shakthimaan.com

  reply	other threads:[~2011-09-09  4:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  5:58 CRC calculation in Module.symvers Shakthi Kannan
2011-09-07 12:54 ` Michal Marek
2011-09-09  4:50   ` Shakthi Kannan [this message]
2011-09-09 13:17     ` Michal Marek
2011-09-10  2:55       ` Shakthi Kannan
2011-09-07 22:46 ` Paul E. McKenney

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=CABG-yt030LAdqbRySzs8sj0Ajwst_c8RHf7yOyG9Eihh6mmf+w@mail.gmail.com \
    --to=shakthimaan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).