Re: Tainted Modules Help Notices

From: Keith Owens (
Date: Wed Oct 10 2001 - 16:28:36 EST

On Wed, 10 Oct 2001 13:28:21 -0700 (PDT),
"Morgan Collins [Ax0n]" <> wrote:
>I think that the modprobe source and the kernel source just aren't in sync with the
>development of the new (re DEVELOPMENTAL) MOD_LICENSE() implementation.

What makes you say that? The list of GPL compatible license strings is
in include/linux/module.h, modutils uses *exactly* the same set of
strings. If somebody uses a different string, their license is not

>If the purpose was to discriminate against licensing, I would agree. But since
>non-compatible source is not distributed with the kernel, and the mechanism is for
>debugging, what is the purpose of lying to the kernel? To confuse debuggers? No point in that.

To triage bug reports. Any bug report against a tainted kernel is
almost certain to be bounced with "your kernel contains code that we do
not have the source for, send this bug report to the company that
maintains the non-GPL code".

>> Just out of curiosity do all of these license tags in the modules take
>> up any permanent kernel memory, especially in a heavily modularize system?

No, they are in the modinfo section along with module parms, author,
description, kernel vesrion etc. None of that gets loaded into memory.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:35 EST