Thread (2 messages) 2 messages, 2 authors, 2004-02-19

Re: Non-GPL export of invalidate_mmap_range

From: Andrew Morton <hidden>
Date: 2004-02-19 18:59:00
Also in: lkml

Christoph Hellwig [off-list ref] wrote:
On Wed, Feb 18, 2004 at 03:32:34PM -0800, Andrew Morton wrote:
quoted
quoted
Yes.  We've traditionally not exported symbols unless we had an intree user,
and especially not if it's for a module that's not GPL licensed.
That's certainly a good rule of thumb and we (and I) have used it before.

What is the reasoning behind it?
The reason is that someone who wants to distribute a binary only module
has to show it's module is not a derived work, and someone who needs new
core in the kernel and new exports pretty much shows his work is deeply
integrated with the kernel.
Needing access to invalidate_mmap_range() is surely not an indication of a
derived work.  It is an indication of a need for a reliable way to achieve
inter-node cache consistency.  Other distributed filesystems will need this
and probably AIX already provides it.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help