linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test10-mm1
Date: Wed, 26 Nov 2003 05:29:00 -0800	[thread overview]
Message-ID: <20031126052900.17542bb3.akpm@osdl.org> (raw)
In-Reply-To: <20031126130936.A5275@infradead.org>

Christoph Hellwig <hch@infradead.org> wrote:
>
> On Wed, Nov 26, 2003 at 04:42:51AM -0800, Andrew Morton wrote:
> > The individual patches in the broken-out/ directory are usually
> > changelogged.  This one says:
> > 
> >   It was EXPORT_SYMBOL_GPL(), however IBM's GPFS is not GPL.
> > 
> >   - the GPFS team contributed to the testing and development of
> >     invaldiate_mmap_range().
> > 
> >   - GPFS was developed under AIX and was ported to Linux, and hence meets
> >     Linus's "some binary modules are OK" exemption.
> > 
> >   - The export makes sense: clustering filesystems need it for shootdowns to
> >     ensure cache coherency.
> 
> Have you actually looked at the gpfs glue code?

Nope.

> something that digs that deep
> into the VM and VFS actually _must_ be derived work.

Could be.  I'm surprised that they need a glue layer at all actually.

> Or do wed allow people
> now to pay a developer tax to buy themselves free from GPL restrictions.

Well I think that restructuring the pagecache invalidaton in such a way
that it is useful for non-derived clustered filesytems does give one some
rights to actually use that code.  It seems a bit rude to take the code but
to make it unusable.

> I as one of the collective copytight holders of the kernel strongly disagree
> with that, it can't be true that IBM can just ignore copyright law..

Well if people have problems with it then I don't feel strongly enough
about it to dispute that, frankly.

But I do not think that making a single kernel symbol inaccessible is an
appropriate way of resolving a GPFS licensing dispute.
--
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>

  parent reply	other threads:[~2003-11-26 13:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26  5:15 2.6.0-test10-mm1 Andrew Morton
2003-11-26  8:51 ` 2.6.0-test10-mm1 Christoph Hellwig
2003-11-26 12:42   ` 2.6.0-test10-mm1 Andrew Morton
2003-11-26 13:09     ` 2.6.0-test10-mm1 Christoph Hellwig
2003-11-26 13:21       ` 2.6.0-test10-mm1 William Lee Irwin III
2003-11-26 13:23         ` 2.6.0-test10-mm1 Christoph Hellwig
2003-11-26 13:25           ` 2.6.0-test10-mm1 William Lee Irwin III
2003-11-26 13:29       ` Andrew Morton [this message]
2003-11-26 13:25         ` 2.6.0-test10-mm1 Christoph Hellwig
2003-11-26 16:23           ` 2.6.0-test10-mm1 Martin J. Bligh
2003-11-26 19:07           ` 2.6.0-test10-mm1 Mike Fedyk
2003-11-26 22:28             ` 2.6.0-test10-mm1 Arjan van de Ven
2003-11-26 22:40               ` 2.6.0-test10-mm1 Martin J. Bligh
2003-11-26  9:46 ` 2.6.0-test10-mm1 Prakash K. Cheemplavam
2003-11-26 17:27 ` 2.6.0-test10-mm1 (compile stats) John Cherry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031126052900.17542bb3.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox