public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	agk@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] device-mapper: multipath
Date: Wed, 16 Feb 2005 08:04:37 +0100	[thread overview]
Message-ID: <20050216070437.GA18912@elte.hu> (raw)
In-Reply-To: <20050211133632.2277fed9.akpm@osdl.org>


* Andrew Morton <akpm@osdl.org> wrote:

> Christoph Hellwig <hch@infradead.org> wrote:
> >
> > > +EXPORT_SYMBOL(dm_register_path_selector);
> >  > +EXPORT_SYMBOL(dm_unregister_path_selector);
> > 
> >  I though we agreed to only allow GPL'ed path selectors at OSDL?
> 
> (OSDL?)
> 
> Yup, this should be _GPL.  Anything which uses these exports is a
> derived work, isn't it?

i'd not say it that categorically. I'd rather say that any module which
uses these exports gains access to a wide range of GPL-licensed internal
functionality of the kernel under the condition that the module declares
that it is license-compatible with the GPL.

While the use of such functionality very likely means that the module is
derived work, even if it's not derived work (e.g. consider the following
absurd corner-case: it is a short, trivial binary blob that was
brute-force generated and blackbox tested to be a kernel module that
happens to load fine) the module still has to follow the rules and must
not circumvent the technological protection measure.

(this fine distinction may or may not matter to you legally or
otherwise, depending on your geographical coordinates and other
factors.)

	Ingo

      parent reply	other threads:[~2005-02-16  7:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 17:15 [PATCH] device-mapper: multipath Alasdair G Kergon
2005-02-11 17:31 ` Christoph Hellwig
2005-02-11 21:36   ` Andrew Morton
2005-02-11 21:42     ` Christoph Hellwig
2005-02-11 22:54     ` Alasdair G Kergon
2005-02-16  7:04     ` Ingo Molnar [this message]

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=20050216070437.GA18912@elte.hu \
    --to=mingo@elte.hu \
    --cc=agk@redhat.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.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