> The next version of insmod will warn about modules with no
> MODULE_LICENSE at all and inform about modules with proprietary
> licences. Both cases will mark the kenrel as tainted which will show
> up on bug reports.
That really doesn't make sense. Nothing changes in the kernel or the module
based upon whether you have the source or not. What should logically taint
the kernel are modules that weren't compiled for that exact kernel version
or are otherwise mismatched.
One can make the argument that the kernel is tainted if a module wasn't
compiled on that machine with that kernel version. One can make the argument
that the kernel is tainted if the module was compiled against different
configuration or header files. Once can make the argument that the kernel is
tainted if a module is loaded whose source isn't part of the general Linux
distribution. One can make all sorts of logical arguments about what taints
the kernel, but how can the license of a module taint the kernel?
You can't even argue that if it's GPL, anyone can get the source to debug
it. The GPL does not require that the source code be made available to the
general public. Perhaps the kernel is tainted if that module wasn't built
from source on that machine?
What's the logic here?!
DS
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/