From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 47FB2CE0 for ; Tue, 18 Sep 2018 13:36:01 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DB3E72D4 for ; Tue, 18 Sep 2018 13:36:00 +0000 (UTC) Date: Tue, 18 Sep 2018 09:35:58 -0400 From: Steven Rostedt To: Mauro Carvalho Chehab Message-ID: <20180918093558.7ad355dc@gandalf.local.home> In-Reply-To: <20180917072250.5bbcb736@coco.lan> References: <1591325.98K2JSm7l9@avalon> <7500551.ylj9XQ2o2G@avalon> <20180916221523.GB3575@thunk.org> <20180917072250.5bbcb736@coco.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ksummit Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] EXPORT_SYMBOL_GPL List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 17 Sep 2018 07:22:50 -0300 Mauro Carvalho Chehab wrote: > A common practice there is that, when someone rewrites the implementation > of some symbol using EXPORT_SYMBOL() is to use EXPORT_SYMBOL_GPL() at > the new implementation, to make clear about our desire that media modules > should be GPL'd, but when we do simpler changes (even adding/removing > parameters at the interface), we tend not to change it[1]. To add to this bike-shed discussion, my view is that if the function is unique to Linux, it should be EXPORT_SYMBOL_GPL(), and if it is a common functionality among all operating systems (like request_irq()) then I would consider it EXPORT_SYMBOL(). The tracing infrastructure that we have is unique to Linux and thus all functions are EXPORT_SYMBOL_GPL(). Proprietary modules can't even add trace events without breaking that. Although they could use kprobes and function based events (when we finish that). -- Steve