public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pat Suwalski <pats@xandros.com>
To: henrique@cyclades.com, linux-kernel@vger.kernel.org
Subject: Re: modversion clarification.
Date: Thu, 25 Jul 2002 13:43:43 -0400	[thread overview]
Message-ID: <3D4038CF.4020501@xandros.com> (raw)
In-Reply-To: 200207251359.50615.henrique@cyclades.com

henrique wrote:
> When you try to load the module, the insmod will check if the symbols of your 
> module are the same of the current running kernel. If the symbols are the 
> same the module will be loaded. So you can use your module on all kernels 
> that have the same CRC for the kernel functions your module uses.

So then is that not opposite of what modversion says it does, which is 
to allow modules to be more comptible across multiple kernel versions?

Basically, the problem is that if module.h is included and MODVERSION is 
not defined, and the module wants to export symbols (EXPORT_SYMTAB is 
defined), then module.h automatically ifdefs modversions.h even if the 
kernel is not configured to use it (and thus the file does not exist).

--Pat

> As a matter of fact it happens seldomly as the kernel are always changing and 
> you have to recompile your module every time you change your kernel. But it 
> is still a very good idea.
> 
> regards
> Henrique


  parent reply	other threads:[~2002-07-25 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25 16:17 modversion clarification Pat Suwalski
     [not found] ` <200207251359.50615.henrique@cyclades.com>
2002-07-25 17:43   ` Pat Suwalski [this message]
2002-07-26  2:30     ` Kai Germaschewski
2002-07-25 22:50 ` Alan Cox

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=3D4038CF.4020501@xandros.com \
    --to=pats@xandros.com \
    --cc=henrique@cyclades.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