From: Florin Malita <fmalita@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
proski@gnu.org, linux-kernel@vger.kernel.org
Subject: Re: incorrect taint of ndiswrapper
Date: Fri, 27 Oct 2006 00:32:15 -0400 [thread overview]
Message-ID: <45418BCF.8080108@gmail.com> (raw)
In-Reply-To: <20061025205923.828c620d.akpm@osdl.org>
Andrew Morton wrote:
> May be so. But this patch was supposed to print a helpful taint message to
> draw our attention to the fact that ndis-wrapper was in use. The patch was
> not intended to cause gpl'ed modules to stop loading (or if is was, that
> effect was concealed from yours truly).
>
It's an unintended side effect of recent per-module-taint changes which
exposed the special nature of ndiswrapper & driverloader taints. Here's
where it went wrong:
Florin Malita wrote:
> No need to keep 'license_gplok' around anymore, it should be equivalent
> to !(taints & TAINT_PROPRIETARY_MODULE).
>
That turns out to be true for every module under the sun except
ndiswrapper & driverloader which are singled out and treated
differently: their proprietary taint has nothing to do with their license.
Randy's patch looks like a reasonable compromise to get them going again
- the alternative being the reintroduction of license_gplok or some
equivalent per-module flag just to support 2 hardcoded exceptions where
GPL incompatibility and proprietary tainting are not correlated.
---
fm
next prev parent reply other threads:[~2006-10-27 4:32 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 20:11 incorrect taint of ndiswrapper Pavel Roskin
2006-10-25 20:30 ` Alan Cox
2006-10-25 20:40 ` Kyle Moffett
2006-10-25 21:04 ` Alan Cox
2006-10-25 21:06 ` Pavel Roskin
2006-10-25 21:33 ` David Weinehall
2006-10-25 22:02 ` Pavel Roskin
2006-10-25 22:54 ` Alan Cox
2006-10-25 22:58 ` Alan Cox
2006-10-26 3:23 ` David Weinehall
2006-10-26 13:13 ` Thierry Vignaud
2006-10-26 13:21 ` Gianluca Alberici
2006-10-26 3:59 ` Andrew Morton
2006-10-26 9:03 ` Gianluca Alberici
2006-10-26 10:39 ` Alan Cox
2006-10-26 12:21 ` Giacomo A. Catenazzi
2006-10-26 12:59 ` Gianluca Alberici
2006-10-26 14:41 ` Al Viro
2006-10-26 14:55 ` Alan Cox
2006-10-26 16:00 ` Stephen Hemminger
2006-10-26 16:26 ` Gianluca Alberici
2006-10-27 14:24 ` Arjan van de Ven
2006-10-27 15:14 ` Stephen Hemminger
2006-10-26 19:19 ` Pavel Roskin
2006-10-26 21:46 ` Adrian Bunk
2006-10-26 22:29 ` Pavel Roskin
2006-10-26 23:00 ` Adrian Bunk
2006-10-26 23:36 ` Sven-Haegar Koch
2006-10-27 0:57 ` Adrian Bunk
2006-10-26 23:47 ` Pavel Roskin
2006-10-27 12:52 ` Roland Kuhn
2006-10-27 15:53 ` Pavel Roskin
2006-10-26 17:26 ` [PATCH ??] " Randy Dunlap
2006-10-27 14:23 ` Arjan van de Ven
2006-10-27 15:27 ` Randy Dunlap
2006-10-27 18:26 ` Andrew Morton
2006-10-27 22:56 ` Florin Malita
2006-10-27 22:56 ` Randy Dunlap
2006-10-27 23:05 ` Alan Cox
2006-10-27 23:02 ` Randy Dunlap
2006-10-27 23:12 ` Florin Malita
2006-10-27 23:23 ` Oleg Verych
2006-10-29 11:27 ` Gianluca Alberici
2006-10-27 21:32 ` Florin Malita
2006-10-27 4:32 ` Florin Malita [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-23 5:41 Giridhar Pemmasani
2006-10-23 5:53 ` Gianluca Alberici
2006-10-23 6:25 ` Chase Venters
2006-10-23 6:41 ` Giridhar Pemmasani
2006-10-23 6:48 ` Gianluca Alberici
2006-10-23 7:12 ` Chase Venters
2006-10-23 11:07 ` Giridhar Pemmasani
2006-10-23 9:10 ` Gianluca Alberici
2006-10-23 9:39 ` Michal Schmidt
2006-10-23 8:24 ` Bernd Petrovitsch
2006-10-23 10:41 ` Alan Cox
2006-10-23 11:35 ` Giridhar Pemmasani
2006-10-23 13:00 ` Alan Cox
2006-10-24 2:43 ` Giridhar Pemmasani
2006-10-24 3:11 ` Randy Dunlap
2006-10-24 12:12 ` Pekka Enberg
2006-10-24 12:22 ` Alan Cox
2006-10-24 14:07 ` Alan Cox
2006-10-23 18:36 ` Zan Lynx
2006-10-24 11:59 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45418BCF.8080108@gmail.com \
--to=fmalita@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).