public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	Manfred Spraul <manfred@colorfullife.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] kernel/rcupdate.c: make the exports EXPORT_SYMBOL_GPL
Date: Mon, 4 Apr 2005 14:49:50 -0700	[thread overview]
Message-ID: <20050404214950.GG1297@us.ibm.com> (raw)
In-Reply-To: <1112602705.6270.33.camel@laptopd505.fenrus.org>

On Mon, Apr 04, 2005 at 10:18:24AM +0200, Arjan van de Ven wrote:
> On Sat, 2005-04-02 at 22:02 -0800, Paul E. McKenney wrote:
> 
> > These need to be put back.  Moving them to GPL -- but in a measured
> > manner, as I proposed on this list some months ago -- is fine.  Changing
> > these particular exports precipitously is most definitely -not- fine.
> > Here is my earlier proposal:
> 
> ok so there is no disagreement that these should become _GPL eventually,
> only about the "when".

Agreed.  I would indeed look pretty silly arguing that they should -never-
go _GPL, since I proposed moving in that direction some months ago.  ;-)

>                        There is agreement also about the expectation
> that currently no binary module is using these.

Agreed, in that I know of no binary module that uses RCU.  However,
I cannot -prove- that there is no such module.

>                                                 Personally I would then
> suggest removing them right now (as is done in -bk); the longer you wait
> the higher the chance of anyone out there starting to use them and
> giving/having a problem a year from now, while the current "damage" is
> expected to be zero.

If someone starts using the exports in a binary module given the warnings
("/* WARNING: GPL-only in April 2006. */"), they have done so with the
knowledge that they will need to change.  Therefore, any future "damage"
would be self-inflicted.  Even if they failed to notice the warnings,
IBM would have made a reasonable and conscientious effort to inform them.
In contrast, if the exports change suddenly now, then the (unlikely, but
still possible) "damage" could be argued to be inflicted, indirectly,
by IBM.  I would (and do) vehemently disagree with such an argument,
but my opinion might not count for much.  IANAL, after all.

And of course, these exports are a special case due to the well-known
presence of the RCU patents.

This line of reasoning might seem a bit strange (it certainly did to me at
first!), but I eventually had to admit that it is quite a bit less strange
than some things that have actually happened over the past few years.  :-/

Finally, please note that this is not a "Mr. Binary-Module, you have
a year to complain and maybe change my mind" type of notification.
This is instead a "this change -will- happen, but I am doing you
the courtesy of giving you advance notice of an upcoming change in an
implicit patent license" type of notification.  From the patch:

+       So these will move to GPL after a grace period to allow
+       people, who might be using implementations that I am not aware
+       of, to adjust to this upcoming change.

Fair enough?

							Thanx, Paul

  reply	other threads:[~2005-04-04 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 14:34 [2.6 patch] kernel/rcupdate.c: make the exports EXPORT_SYMBOL_GPL Adrian Bunk
2005-04-03  6:02 ` Paul E. McKenney
2005-04-04  8:18   ` Arjan van de Ven
2005-04-04 21:49     ` Paul E. McKenney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-03 13:23 Adrian Bunk

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=20050404214950.GG1297@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /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