linux-kernel - Re: GPL-incompatible Module Error Message

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f2b55d220704191804g2d5b0d5fl762a411c3edae43d@mail.gmail.com>
Date:	Thu, 19 Apr 2007 18:04:36 -0700
From:	"Michael K. Edwards" <medwards.linux@...il.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	chris@...urn.com, linux-kernel@...r.kernel.org
Subject: Re: GPL-incompatible Module Error Message

On 4/19/07, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> The troll is back I see.

Troll, shmoll.  I call 'em like I see 'em.  As much as I like and
depend on Linux, and as much as I respect the contributions and the
ideals of the EXPORT_SYMBOL_GPL partisans, they're spreading needless
FUD by spraying "private-don't-touch-me" all over mechanisms that are
_explicitly_designed_ as interoperation boundaries.  They're also
aiding and abetting the FSF's hypocritical charlatanry about the
meaning of "derivative work".

> Why don't you give him some useful information instead

Alternate technical solutions are also useful.  You seem to know them;
I don't pretend to.  Thanks for providing them.

> - Turn off the paravirt option - you don't need it, and its just bloat
> and slows down the kernel. Then rebuild the kernel and other bits and it
> should all work fine.

Just out of curiosity -- it seems thoroughly unlikely that ATI has
intentionally touched paravirt_ops in fglrx.  Do you think that
redefining bog-standard Linux interfaces when CONFIG_PARAVIRT (or
whatever) is enabled suddenly makes fglrx a derivative work of
whatever code underlies paravirt_ops?

> The legality of the ati driver as a derivative work is another matter,
> but I don't see what _GPL symbols have to do with its legality beyond
> providing a hint.

Then surely you don't approve of spraying FATAL messages on people's
consoles under these circumstances.  Allowing code into one's kernel
whose integration problems can't or won't be diagnosed by mainline
developers may be foolish, but it's not FATAL.

Cheers,
- Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/