From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc2-mm2
Date: Mon, 11 Apr 2005 08:18:32 -0700 [thread overview]
Message-ID: <20050411151832.GA1301@us.ibm.com> (raw)
In-Reply-To: <20050410224834.GK4204@stusta.de>
On Mon, Apr 11, 2005 at 12:48:34AM +0200, Adrian Bunk wrote:
> kernel-rcupdatec-make-the-exports-export_symbol_gpl.patch
> add-deprecated_for_modules.patch
> add-deprecated_for_modules-fix.patch
> deprecate-synchronize_kernel-gpl-replacement.patch
> deprecate-synchronize_kernel-gpl-replacement-fix.patch
> change-synchronize_kernel-to-_rcu-and-_sched.patch
>
>
> Please drop these patches.
Please keep them!
> Using these symbols in non-GPL modules is a legal problem at least in
> the USA except for IBM,
Again, based on what line of reasoning? Again, the obvious lines
of reasoning do not apply.
> and all we've heard from IBM is that they are
> not 100% sure that there is really no binary-only module by IBM that
> might use these symbols.
>From my earlier message (http://lkml.org/lkml/2005/4/4/244):
Agreed, in that I know of no binary module that uses RCU. However,
I cannot -prove- that there is no such module.
IOW, I am also not 100% sure that there is really no binary-only module
using these symbols by -anyone-, including someone -other- than IBM.
In addition, I know of no way that -anyone- could possibly be 100% sure
that there is really no binary-only module using symbols. Hence the
approach of providing the year "grace period" before transitioning to
EXPORT_SYMBOL_GPL().
> The risk of anyne using them only increases (no matter that it's marked
> as deprecated) as long as it's available - and nobody has until now
> claimed that he's actually using one pf them in a binary-only module.
I am not convinced that the risk of usage increases significantly.
However, even if someone does start using them in a binary module, they
will have been warned. Yes, someone could possibly ignore the warning.
They -still- will have been warned, so that any "damage" would be
self-inflicted. Therefore, as noted earlier, the symbol transitions
to EXPORT_SYMBOL_GPL() one year after its inclusion, regardless of any
people who ignored warnings.
Thanx, Paul
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
>
next prev parent reply other threads:[~2005-04-11 15:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 10:08 2.6.12-rc2-mm2 Andrew Morton
2005-04-08 11:46 ` 2.6.12-rc2-mm2 Rafael J. Wysocki
2005-04-08 16:44 ` 2.6.12-rc2-mm2 Rafael J. Wysocki
2005-04-08 12:25 ` 2.6.12-rc2-mm2 Indrek Kruusa
2005-04-08 14:11 ` 2.6.12-rc2-mm2 Jan Dittmer
2005-04-08 15:23 ` 2.6.12-rc2-mm2 Paulo Marques
2005-04-08 14:14 ` 2.6.12-rc2-mm2 Jan Dittmer
2005-04-08 22:21 ` 2.6.12-rc2-mm2 Andrew Morton
2005-04-08 15:17 ` 2.6.12-rc2-mm2 Alexander Nyberg
2005-04-08 17:28 ` 2.6.12-rc2-mm2 Alexey Dobriyan
2005-04-08 13:52 ` 2.6.12-rc2-mm2 Martin Waitz
2005-04-08 23:28 ` 2.6.12-rc2-mm2 Jesper Juhl
2005-04-09 1:49 ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-09 1:57 ` 2.6.12-rc2-mm2 Jesper Juhl
2005-04-09 12:51 ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-09 13:43 ` 2.6.12-rc2-mm2 Alexander Nyberg
2005-04-10 13:31 ` 2.6.12-rc2-mm2 Alexander Nyberg
2005-04-10 22:48 ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-11 15:18 ` Paul E. McKenney [this message]
2005-04-13 0:36 ` 2.6.12-rc2-mm2 Adrian Bunk
2005-04-13 1:32 ` 2.6.12-rc2-mm2 Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 11:50 2.6.12-rc2-mm2 Michael Thonke
2005-04-10 15:06 2.6.12-rc2-mm2 Pavel Machek
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=20050411151832.GA1301@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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