Re: 2.6: problem with module tainting the kernel

[li nux <lnxluv@yahoo.com>]

Thanks to Randy and everyone who replied.
Yes, I am using SuSE kernel.
On building the module it successfully generates
hello.ko.
Here is the message I get on doing a insmod of
hello.ko:

"Jun 12 14:47:56 myhost kernel: hello: unsupported
module, tainting kernel."

Here is the code

#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/init.h>
#include <linux/version.h>
#include <linux/vermagic.h>

static int __init hello_init (void)
{
        printk("module hello loading");
        return 0;
}

static void __exit hello_exit (void)
{
        printk("module hello exiting");
}

module_init(hello_init);
module_exit(hello_exit);
MODULE_LICENSE ("GPL");

--- randy_dunlap <rdunlap@xenotime.net> wrote:

> On Fri, 10 Jun 2005 08:24:50 -0700 (PDT) li nux
> wrote:
> 
> | In 2.6 kernels how to assure that on inserting our
> own
> | module, it doesn't throw the warning:
> | 
> | "unsupported module, tainting kernel"
> 
> That string is not in the kernel source code that I
> can see.
> Be more precise, please.
> 
> 
> | what tainting depends on apart from the license
> string ?
> 
> load:
> 
> - CONFIG_MODVERSIONS is set but some symbol does not
> have
>   version info
> 
> - a license that is not GPL-compatible
> 
> - no version magic info for the module
> 
> unload:
> 
> - forcefully unloading a module
> 
> ---
> ~Randy
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com