Re: [PATCH] Blacklist binary-only modules lying about their license

Timothy Miller
2004-04-29T22:58:30Z

Marc Boucher wrote:

>
> The proprietary modem code for the HSF driver is not part of the kernel,
> nor did its original developers ever intend for it to be run by the
> Linux kernel.
>
> Whether proprietary binary-only code is dynamically loaded through the
> module subsystem or physically by someone installing a card is a
> technicality with little relevance.

So, what you're saying is that you have taken a binary driver, not
written by you, designed for an entirely different ABI, and you have
written some code, which you have released under GPL, that interfaces
between the Linux Kernel and the binary driver?

Kinda like that project which lets people use Windows network drivers
under Linux?

I don't see a problem with that, ideologically. I mean, it sucks that
we can't get Linux-specific drivers, but at least people can use the
hardware.

HOWEVER, there are two problems:

(1) It still taints the kernel, because the behavior of the Windows
driver is still a black box that cannot be debugged. The only way to
avoid that would be to run the Windows driver in some kind of sandbox.

(2) Misleading the kernel (and users) into thinking that the driver does
not taint the kernel, when in fact it does, is wrong.

You have pointed out an interesting point in another email. I have to
agree that, technically, thunking to BIOS code also taints the kernel,
because it, too, is a black box which could corrupt the kernel. What do
others have to say about that?