linux-kernel - Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols

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: <alpine.LFD.1.00.0802291224290.17889@woody.linux-foundation.org>
Date:	Fri, 29 Feb 2008 12:28:13 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Pavel Roskin <proski@....org>
cc:	Zan Lynx <zlynx@....org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jon Masters <jcm@...masters.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only
 symbols

On Fri, 29 Feb 2008, Pavel Roskin wrote:
> 
> This still leaves us with the workqueue interface:
> 
> __create_workqueue_key
> destroy_workqueue
> flush_workqueue
> queue_work

Hmm. Personally, I don't see those as being a big issue, but they've been 
marked GPL-only for a long while. 

The thing is, I personally don't mind, and I think "derived code" is what 
matters, but others disagree, and quite frankly, I'm not going to force 
them - I have my _personal_ beliefs, but hey, others have theirs.

So you really need to talk to not me, but to the people who actually wrote 
and maintain that code. When they come back and say "yeah, we think 
ndiswrapper is a special case and we're ok with it", I'll happily either 
mark those things non-GPL or just mark ndiswrapper special in the module 
loader again.

Quite frankly, I don't care about ndiswrapper enough (at all) to push this 
along in the least. 

		Linus
--
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/