* loading ./cryptfs.o will taint the kernel
@ 2002-03-09 22:13 brian
2002-03-09 22:38 ` Alan Cox
0 siblings, 1 reply; 2+ messages in thread
From: brian @ 2002-03-09 22:13 UTC (permalink / raw)
To: linux-kernel
loading ./cryptfs.o will taint the kernel: non-GPL license - LGPL
I have long thought that I understood the reasoning behind "taint" and
binary drivers.
However, cryptfs is available with complete source code, so I presume
the "undebug-able" argument doesn't apply.
So what is the big deal?
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: loading ./cryptfs.o will taint the kernel
2002-03-09 22:13 loading ./cryptfs.o will taint the kernel brian
@ 2002-03-09 22:38 ` Alan Cox
0 siblings, 0 replies; 2+ messages in thread
From: Alan Cox @ 2002-03-09 22:38 UTC (permalink / raw)
To: brian; +Cc: linux-kernel
> loading ./cryptfs.o will taint the kernel: non-GPL license - LGPL
>
> I have long thought that I understood the reasoning behind "taint" and
> binary drivers.
>
> However, cryptfs is available with complete source code, so I presume
> the "undebug-able" argument doesn't apply.
>
> So what is the big deal?
Sounds like someone put the wrong MODULE_LICENSE() tag on it. An LGPL item
combined with a GPL work gives you a GPL result (see the LGPL notes on the
matter). So the kernel module tag ought to be GPL
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-03-09 22:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-03-09 22:13 loading ./cryptfs.o will taint the kernel brian
2002-03-09 22:38 ` Alan Cox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®