public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Al Viro <viro@ftp.linux.org.uk>, Pavel Roskin <proski@gnu.org>,
	Aaditya.Rai@atheros.com, Prem.Kumar@atheros.com,
	Stephen.Chen@atheros.com, Rahul.Sridhar@atheros.com,
	Allen.Tsai@atheros.com
Subject: Re: EXPORT_SYMBOL_GPL recursive for shim and/or wrappers
Date: Mon, 1 Jun 2009 14:39:37 -0700	[thread overview]
Message-ID: <20090601213937.GA29774@kroah.com> (raw)
In-Reply-To: <43e72e890906011241u24b82cc3gc06bf7be4f43075e@mail.gmail.com>

On Mon, Jun 01, 2009 at 12:41:58PM -0700, Luis R. Rodriguez wrote:
> Does EXPORT_SYMBOL_GPL imply that modules which make use of these
> symbols must also use EXPORT_SYMBOL_GPL for their own symbols? If so
> then it would be clear of the recursive nature of intent.

I have had a group of lawyers and law-students study this very topic a
lot in the past.  It comes down to "intent".  If you are creating a
"shim" kernel module to merely export the symbols into the "non-gpl"
namespace, the "intent" of such a piece of code is to obviously
circumvent the original "intent" of the GPL-only marking.

This argument was successfully used to cause at least one company to
stop doing this very thing.

Now if you try to explicitly document this somehow, well, I think you
fall into the old "try to explicitly define everything" problem, which
is counterproductive as people try to work around such definitions.  I
say leave it as-is, and let my lawyers have fun if anyone tries to abuse
it :)

thanks,

greg k-h

      parent reply	other threads:[~2009-06-01 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 19:41 EXPORT_SYMBOL_GPL recursive for shim and/or wrappers Luis R. Rodriguez
2009-06-01 20:37 ` Pavel Roskin
2009-06-01 21:32 ` Alan Cox
2009-06-01 21:39 ` Greg KH [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=20090601213937.GA29774@kroah.com \
    --to=greg@kroah.com \
    --cc=Aaditya.Rai@atheros.com \
    --cc=Allen.Tsai@atheros.com \
    --cc=Prem.Kumar@atheros.com \
    --cc=Rahul.Sridhar@atheros.com \
    --cc=Stephen.Chen@atheros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=proski@gnu.org \
    --cc=viro@ftp.linux.org.uk \
    /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