* 2.6: problem with module tainting the kernel
@ 2005-06-10 15:24 li nux
2005-06-10 15:35 ` Christoph Hellwig
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: li nux @ 2005-06-10 15:24 UTC (permalink / raw)
To: linux
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6: problem with module tainting the kernel
2005-06-10 15:24 2.6: problem with module tainting the kernel li nux
@ 2005-06-10 15:35 ` Christoph Hellwig
2005-06-11 3:11 ` randy_dunlap
2005-06-11 3:18 ` randy_dunlap
2005-06-11 21:42 ` Carsten Otte
2 siblings, 1 reply; 7+ messages in thread
From: Christoph Hellwig @ 2005-06-10 15:35 UTC (permalink / raw)
To: li nux; +Cc: linux
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?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6: problem with module tainting the kernel
2005-06-10 15:35 ` Christoph Hellwig
@ 2005-06-11 3:11 ` randy_dunlap
0 siblings, 0 replies; 7+ messages in thread
From: randy_dunlap @ 2005-06-11 3:11 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: lnxluv, linux-kernel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6: problem with module tainting the kernel
2005-06-10 15:24 2.6: problem with module tainting the kernel li nux
2005-06-10 15:35 ` Christoph Hellwig
@ 2005-06-11 3:18 ` randy_dunlap
2005-06-12 9:25 ` li nux
2005-06-11 21:42 ` Carsten Otte
2 siblings, 1 reply; 7+ messages in thread
From: randy_dunlap @ 2005-06-11 3:18 UTC (permalink / raw)
To: li nux; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6: problem with module tainting the kernel
2005-06-10 15:24 2.6: problem with module tainting the kernel li nux
2005-06-10 15:35 ` Christoph Hellwig
2005-06-11 3:18 ` randy_dunlap
@ 2005-06-11 21:42 ` Carsten Otte
2 siblings, 0 replies; 7+ messages in thread
From: Carsten Otte @ 2005-06-11 21:42 UTC (permalink / raw)
To: li nux; +Cc: linux
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6: problem with module tainting the kernel
2005-06-11 3:18 ` randy_dunlap
@ 2005-06-12 9:25 ` li nux
2005-06-12 15:31 ` Carlos Martin
0 siblings, 1 reply; 7+ messages in thread
From: li nux @ 2005-06-12 9:25 UTC (permalink / raw)
To: randy_dunlap; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: 2.6: problem with module tainting the kernel
2005-06-12 9:25 ` li nux
@ 2005-06-12 15:31 ` Carlos Martin
0 siblings, 0 replies; 7+ messages in thread
From: Carlos Martin @ 2005-06-12 15:31 UTC (permalink / raw)
To: li nux; +Cc: randy_dunlap, linux-kernel
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2005-06-12 15:31 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-06-10 15:24 2.6: problem with module tainting the kernel li nux
2005-06-10 15:35 ` Christoph Hellwig
2005-06-11 3:11 ` randy_dunlap
2005-06-11 3:18 ` randy_dunlap
2005-06-12 9:25 ` li nux
2005-06-12 15:31 ` Carlos Martin
2005-06-11 21:42 ` Carsten Otte
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox