2.6: problem with module tainting the kernel

2.6: problem with module tainting the kernel

[li nux]

In 2.6 kernels how to assure that on inserting our own
module, it doesn't throw the warning:

"unsupported module, tainting kernel"

what tainting depends on apart from the license string ?


		
__________________________________ 
Yahoo! Mail Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone. 
http://mobile.yahoo.com/learn/mail 

Re: 2.6: problem with module tainting the kernel

[Christoph Hellwig]

On Fri, Jun 10, 2005 at 08:24:50AM -0700, 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"

There's no place in the kernel that produces this message.  Are you
using some odd vendor tree?

Re: 2.6: problem with module tainting the kernel

[randy_dunlap]

On Fri, 10 Jun 2005 16:35:06 +0100 Christoph Hellwig wrote:

| On Fri, Jun 10, 2005 at 08:24:50AM -0700, 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"
| 
| There's no place in the kernel that produces this message.  Are you
| using some odd vendor tree?

to put it another way, show us all of the kernel
messages from when you try to load the module.

---
~Randy

Re: 2.6: problem with module tainting the kernel

[randy_dunlap]

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

Re: 2.6: problem with module tainting the kernel

[li nux]

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 

Re: 2.6: problem with module tainting the kernel

[Carlos Martin]

On 12/06/05, li nux <lnxluv@yahoo.com> wrote:
> 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."
 This means that the module is unsupported by SuSE/Novell and
therefore vendor-tainted. It does not mean that the kernel is tainted
in the canonical way. IIRC there are different types of tainting, and
this is just one of them.

-- 
Carlos Martín         http://www.cmartin.tk   http://rpgscript.berlios.de

Nowadays everyting has infrared and wireless. If it's big enough, it
gets Gigabit and a DVD burner.

Re: 2.6: problem with module tainting the kernel

[Carsten Otte]

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"
>
>what tainting depends on apart from the license string ?
>  
>
Guess you're using a SuSE Kernel? That one gets tainted once you
load a module that SuSE does not support (meaning, you cannot call
them and complain about the module). No technical problem.

cheers,
Carsten