Re: Non-GPL export of invalidate_mmap_range

[Tim Bird]

Christoph Hellwig wrote:
> On Wed, Feb 18, 2004 at 04:28:58PM -0800, Andrew Morton wrote: 
> > OK, so I looked at the wrapper.  It wasn't a tremendously pleasant
> > experience.  It is huge, and uses fairly standard-looking filesytem
> > interfaces and locking primitives.  Also some awareness of NFSV4 for some
> > reason.
> >
> > Still, the wrapper is GPL so this is not relevant.
>
> Well, something that needs an almost one megabyte big wrapper per defintion
> is not a standalone work but something that's deeply interwinded with
> the kernel.  The tons of kernel version checks certainly show it's poking
> deeper than it should.
> ...
>
> Something that pokes deep into internal structures and even
> needs new exports certainly is a derived work. 

I'd argue (again) that having a complex glue layer is not evidence
per se of the glued module being a derived work.  If anything,
it is evidence to the contrary.  But it depends on the circumstances.

The question for GPFS itself is whether it was modified to run with
Linux, and how it was modified, and how much it was modified.

If your argument is that Linux, after being modified with the glue
layer, is now a derivative work of the glued module, that seems
more likely.  I'm not sure how the GPL reads on that case.

=============================
Tim Bird
Architecture Group Co-Chair
CE Linux Forum
Senior Staff Engineer
Sony Electronics
E-mail: Tim.Bird@xxxxxxxxxxx
=============================

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/