linux-kernel - Re: Dual-licensing LTTng, marker and tracepoints under GPLv2+/LGPLv2.1+

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]

Date:	Wed, 24 Jun 2009 10:33:34 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	Christoph Hellwig <hch@...radead.org>
Cc:	Pierre-Marc Fournier <pierre-marc.fournier@...ymtl.ca>,
	Tom Zanussi <tzanussi@...il.com>, karim@...rsys.com,
	Michel Dagenais <michel.dagenais@...ymtl.ca>,
	ltt-dev@...ts.casi.polymtl.ca,
	Lai Jiangshan <laijs@...fujitsu.com>,
	kosaki.motohiro@...fujitsu.com, linux-kernel@...r.kernel.org,
	Steven Rostedt <rostedt@...dmis.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Robert Wisniewski <bob@...son.ibm.com>
Subject: Re: Dual-licensing LTTng, marker and tracepoints under
	GPLv2+/LGPLv2.1+


* Mathieu Desnoyers <compudj@...stal.dyndns.org> wrote:

> Hi,
> 
> We want to re-license LTTng as
> 
>   dual-license GPLv2 (or better)/LGPLv2.1 (or better)
> 
> to facilitate code exchange between the GPLv2 LTTng kernel tracer 
> and LGPLv2.1 userspace LTTng tracing library.  This will also 
> include kernel/marker.c, include/linux/marker.h, 
> kernel/tracepoint.c and include/linux/tracepoint.h. For the LTTng 
> tree, everything under the ltt/ subdirectory is targeted.
> 
> I am the main author of most of these files, and I allow such 
> license change as far as my code is concerned. Additionally, we 
> need the approval of most people who contributed code to either 
> LTTng, Linux Kernel Marker and Tracepoints.

Why dont you license the user-space library under the GPLv2?

Also, i dont agree that such interfaces should be ABIs, hence i 
oppose the librarization of such raw kernel interfaces. For example 
markers will be removed in the future, and tracepoints will sure 
undergo more corrective iterations as well.

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