linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bas Mevissen <ml@basmevissen.nl>
To: Kendall Bennett <KendallB@scitechsoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel module symbol versioning?
Date: Mon, 25 Aug 2003 15:03:18 +0200	[thread overview]
Message-ID: <3F4A0916.3010906@basmevissen.nl> (raw)
In-Reply-To: <3F461DF4.26519.490C74E@localhost>

Kendall Bennett wrote:

> Hi,
> 
> I have been reading the book "Linux Device Drivers, 2nd Edition" and have 
> some questions about symbol versioning. In Chapter 11 it mentions that 
> you can use the <linux/modversions.h> header file to compile your module 
> with symbol versions enabled, so that your module will load on multiple 
> kernels and fail if the symbol CRC's do not match. I tested this out on a 
> simple test module, but this module fails to load unless I pass the '-f' 
> flag to insmod (Red Hat 7.3 and 8.0). 
> 
> Is there a way to compile the module so that insmod will only complain if 
> there is a version conflict? Or do you always have to use -f in this case 
> to force the module to load? If you have to do that, will -f still fail 
> to load if the versioned symbols don't match?
> 

Isn't the confict cause here (just) that one is compiled with gcc 2.x 
and the other with gcc 3.x?

In other words, retry compiling this module on one system with the two 
different kernels, as you want to compare kernel source level interface 
  differences and not kernel ABI (Application Binairy Interface IIRC) 
differences.

Regards,

Bas.




      reply	other threads:[~2003-08-25 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22 20:43 Kernel module symbol versioning? Kendall Bennett
2003-08-25 13:03 ` Bas Mevissen [this message]

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=3F4A0916.3010906@basmevissen.nl \
    --to=ml@basmevissen.nl \
    --cc=KendallB@scitechsoft.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;
as well as URLs for NNTP newsgroup(s).