On Thu, May 21, 2015 at 05:33:21PM -0500, Bjorn Helgaas wrote: > > I tentatively put this (and the rest of the series) on a pci/resource > branch. I'm hoping you'll propose some clarification about > EXPORT_SYMBOL_GPL(). EXPORT_SYMBOL_GPL() also serves to ensure only GPL modules can only run that code. So for instance although we have "Dual BSD/GPL" tags for modules pure "BSD" tags do not exist for module tags and cannot run EXPORT_SYMBOL_GPL() code [0]. Also there is some folks who do believe tha at run time all kernel modules are GPL [1] [2]. And to be precise even though the FSF may claim a list of licenses are GPL-compatible we cannot rely on this list alone for our own goals and if folks want to use our EXPORT_SYMBOL_GPL()s they must discuss this on lkml [2]. In the past when I've tried to try to clarify EXPORT_SYMBOL_GPL() requirements, implications, its been said that its best to leave some things as-is [3] and let attorneys figure things out. In so far as to what exactly it is and can be used for requires legal attorney review, but the question of derivative work certainly comes up [4]. Now folks companies seem to want to obviously use and abuse our symbols despite of all the things above, for instance Red Hat once tried to change an EXPORT_SYMBOL_GPL() to EXPORT_SYMBOL() [5]. Obviously that didn't go so well, and some folks went off on a good rant about this [6]. What developers do and accept varies, I'm not going into pointing out specifics and I do not wnat to do homework for folks who wish to abuse things further, but by no means should a developer be nack'd entry to new code if their functionality is not replacing old one [9]. In this case this is new functionality. Also in terms of preference: "nobody has said that symbols exported with plain EXPORT_SYMBOL() can be freely used by proprietary code; indeed, a number of developers claim that all (or nearly all) loadable modules are derived products of the kernel regardless of whether they use GPL-only symbols or not" [7]. And spot on: "In general, the kernel community has long worked to maintain a vague and scary ambiguity around the legal status of proprietary modules while being unwilling to attempt to ban such modules outright." [7]. Now, a few maintainers insist on tons of new symbols to be EXPORT_SYMBOL_GPL() though proactively [8] [9] and the reasons vary, I just happen to also write my code to be perfectly clear with my goals and intent and you are the first to ask me to reconsider this, even if you do make me use EXPORT_SYMBOL() my intent and goal does not change, as with others. No code I ever write should be used by proprietary shit, and I hope to convince others of the importance to do this as well. > In the meantime, I tried to make the changelog a bit more concise, as > below. Let me know if I omitted something essential. We still have URLs > for the discussion for the fine points. Looks good. [0] https://lkml.org/lkml/2012/4/7/102 [1] https://lkml.org/lkml/2012/4/8/71 [2] https://lkml.org/lkml/2012/4/8/71 [3] https://lkml.org/lkml/2009/6/1/385 [4] https://lkml.org/lkml/2009/6/1/376 [5] https://lkml.org/lkml/2012/4/20/328 [6] https://plus.google.com/+AlanCoxLinux/posts/D2feRNc6R4d [7] https://lwn.net/Articles/603131/ [8] https://lwn.net/Articles/603139/ [9] https://lkml.org/lkml/2015/2/26/379 Luis -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
