From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Anton Altaparmakov <anton@tuxera.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Christoph Hellwig" <hch@infradead.org>,
"Szabolcs Szakacsits" <szaka@tuxera.com>,
"Janne Kalliomäki" <janne@tuxera.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Direct i/o changes break all non-GPL file systems
Date: Wed, 8 Feb 2012 00:15:19 +0000 [thread overview]
Message-ID: <20120208001519.501b6fea@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <92291682-5422-4AE2-9608-97775603E7FD@tuxera.com>
On Wed, 8 Feb 2012 00:07:15 +0000
Anton Altaparmakov <anton@tuxera.com> wrote:
> Hi Linus, Andrew, Christoph,
>
> With kernel 3.1, Christoph removed i_alloc_sem and replaced it with calls (namely inode_dio_wait() and inode_dio_done()) which are EXPORT_SYMBOL_GPL() thus they cannot be used by non-GPL file systems and further inode_dio_wait() was pushed from notify_change() into the file system ->setattr() method but no non-GPL file system can make this call.
I'm advised by my lawyer that when this occurs that I should always
inform the other party the following
"For a Linux kernel containing any code I own the code is under the GNU
public license v2 (in some cases or later), I have never given permission
for that code to be used as part of a combined or derivative work which
contains binary chunks. I have never said that modules are somehow
magically outside the GPL and I am doubtful that in most cases a work
containing binary modules for a Linux kernel is compatible with the
licensing, although I accept there may be some cases that it is."
So unless your code is remarkably non-derivative I don't see that
anything has changed.
next prev parent reply other threads:[~2012-02-08 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 0:07 Direct i/o changes break all non-GPL file systems Anton Altaparmakov
2012-02-08 0:15 ` Alan Cox [this message]
2012-02-08 0:28 ` Anton Altaparmakov
2012-02-08 1:51 ` Andreas Dilger
2012-02-10 19:28 ` Linus Torvalds
2012-02-10 21:19 ` Al Viro
2012-02-11 16:18 ` Andi Kleen
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=20120208001519.501b6fea@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=anton@tuxera.com \
--cc=hch@infradead.org \
--cc=janne@tuxera.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szaka@tuxera.com \
--cc=torvalds@linux-foundation.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