From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: zhonglei <zhonglei@RCS-9000.COM>
Cc: linux-kernel@vger.kernel.org
Subject: Re: module mismatch
Date: Fri, 20 May 2005 09:09:59 +0200 [thread overview]
Message-ID: <20050520070959.GS2417@lug-owl.de> (raw)
In-Reply-To: <200505201127.AA8126754@RCS-9000.COM>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On Fri, 2005-05-20 11:27:14 +0800, zhonglei <zhonglei@RCS-9000.COM> wrote:
> when I use "insmod -f hello.o" in my Embeded linux,the warning appears:
> Warning: Kernel-module version mismatch
> hello.o was compiled for kernel version 2.4.24-per2
> while this kernel is version 2.4.25
> Warning: loading hello.o will taint the kernel: forced load
> see http://www.tux.org/lkml/#export-tainted for information about tainted modules
>
> Is there any problem on my using my module function with this warning?
Yes, there is. Your running kernel differs from that one which you
compiled the module sources with. Linux' internal interfaces and data
structures change every now and then, which will result in different
offsets, wrong functions called and the like. You'd *always* compile a
module exactly with the same sources, compiler and .config file to match
the kernel to which you want to load the module.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-05-20 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 3:27 zhonglei
2005-05-20 7:09 ` Jan-Benedict Glaw [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=20050520070959.GS2417@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zhonglei@RCS-9000.COM \
/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
Powered by JetHome