From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
mingo@elte.hu, viro@parcelfarce.linux.theplanet.co.uk,
paulmck@us.ibm.com, arjan@infradead.org,
linux-kernel@vger.kernel.org, jtk@us.ibm.com, wtaber@us.ibm.com,
pbadari@us.ibm.com, markv@us.ibm.com, greghk@us.ibm.com,
torvalds@osdl.org
Subject: Re: [PATCH] fs: Restore files_lock and set_fs_root exports
Date: Sat, 8 Jan 2005 00:32:47 +0100 [thread overview]
Message-ID: <20050107233246.GH14108@stusta.de> (raw)
In-Reply-To: <20050107140034.46aec534.akpm@osdl.org>
On Fri, Jan 07, 2005 at 02:00:34PM -0800, Andrew Morton wrote:
>
> No, I'd say that unexports are different. They can clearly break existing
> code and so should only be undertaken with caution, and with lengthy notice
> if possible.
>
> And it _is_ possible here, because there are no plans to change the
> exported functions, and it's only two lines of code, dammit.
>
> The cost to us of maintaining those two lines of code for a year is
> basically zero.
>
> The cost to others of us removing those two lines of code without warning
> is appreciable.
>
> Obvious solution: don't remove the two lines of code without warning.
>
> The only reason I can see for peremptorily removing those two lines of code
> is that there is some benefit to doing so which outweighs the downstream
> cost of doing so. Nobody has demonstrated such a benefit.
>...
I did a bit research using grep, sort, uniq and wc:
between 2.6.9 and 2.6.10:
414 EXPORT_SYMBOL's were removed
since 2.6.10:
90 EXPORT_SYMBOL's were removed in Linus' tree
in 2.6.10-mm2 excluding linus.patch:
71 EXPORT_SYMBOL's are removed
Notes:
- EXPORT_SYMBOL_GPL's weren't counted in any way
- if an EXPORT_SYMBOL was moved, it wasn't counted (using uniq)
- small mistakes in the numbers might be possible since my method to
measure them was't at a scientific level, but after a quick look
it seems the numbers are roughly correct
Resurrecting and documenting all of these recently removed
EXPORT_SYMBOL's because some company might have found some way to
(ab)use one or more of them costs us:
- some extra work
- wasts space for all users of Linux (e.g. some of the recent removals
are "remove EXPORT_SYMBOL'ed but completely unused function" patches
I sent)
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-01-07 23:36 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 19:05 Paul E. McKenney
2005-01-06 19:13 ` Christoph Hellwig
2005-01-06 20:07 ` Paul E. McKenney
2005-01-06 20:13 ` Christoph Hellwig
2005-01-06 20:35 ` Mike Waychison
2005-01-06 20:59 ` Christoph Hellwig
2005-01-06 21:35 ` Greg KH
2005-01-06 19:14 ` Al Viro
2005-01-06 20:13 ` Paul E. McKenney
2005-01-06 19:20 ` Arjan van de Ven
2005-01-06 20:15 ` Paul E. McKenney
2005-01-06 20:32 ` Al Viro
2005-01-06 21:04 ` Paul E. McKenney
2005-01-06 21:24 ` Al Viro
2005-01-06 23:26 ` Andrew Morton
2005-01-06 23:11 ` Alan Cox
2005-01-07 0:24 ` Linus Torvalds
2005-01-07 0:48 ` Christoph Hellwig
2005-01-07 7:38 ` Arjan van de Ven
2005-01-06 23:41 ` Christoph Hellwig
2005-01-07 0:29 ` Andrew Morton
2005-01-07 0:26 ` Christoph Hellwig
2005-01-07 3:30 ` Mike Waychison
2005-01-07 9:00 ` Ingo Molnar
2005-01-07 9:15 ` Christoph Hellwig
2005-01-07 12:14 ` Antonio Vargas
2005-01-07 22:00 ` Andrew Morton
2005-01-07 22:19 ` Christoph Hellwig
2005-01-07 22:58 ` Andrew Morton
2005-01-08 15:45 ` Alan Cox
2005-01-07 22:49 ` Alan Cox
2005-01-08 0:12 ` Andrew Morton
2005-01-08 2:20 ` Paul E. McKenney
2005-01-07 23:32 ` Adrian Bunk [this message]
2005-01-08 13:10 ` Al Viro
2005-01-07 1:34 ` Alan Cox
2005-01-07 3:17 ` Andrew Morton
2005-01-07 8:12 ` Christoph Hellwig
2005-01-06 23:56 ` [PATCH] add feature-removal-schedule.txt documentation Greg KH
2005-01-07 0:23 ` Christoph Hellwig
2005-01-07 0:32 ` Greg KH
2005-01-07 17:02 ` Randy.Dunlap
2005-01-07 17:54 ` Linus Torvalds
2005-01-07 18:11 ` Greg KH
2005-01-11 12:23 ` [PATCH] cpufreq 2.4 interface removal schedule [Was: Re: [PATCH] add feature-removal-schedule.txt documentation] Dominik Brodowski
2005-01-12 18:41 ` Greg KH
2005-01-07 23:58 ` [PATCH] add feature-removal-schedule.txt documentation Dominik Brodowski
2005-01-12 18:41 ` Greg KH
2005-01-08 18:32 ` Paul E. McKenney
2005-01-08 21:46 ` Alan Cox
2005-01-08 23:03 ` Arjan van de Ven
2005-01-09 6:23 ` Paul E. McKenney
2005-01-09 6:27 ` Paul E. McKenney
2005-01-07 2:02 ` [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-07 1:01 ` Paul E. McKenney
2005-01-07 1:20 ` Al Viro
2005-01-13 2:51 ` Paul E. McKenney
2005-01-13 7:35 ` Arjan van de Ven
2005-01-13 17:53 ` Paul E. McKenney
2005-01-13 17:07 ` Greg KH
2005-01-13 17:44 ` Paul E. McKenney
2005-01-13 17:55 ` Greg KH
2005-01-13 18:29 ` Paul E. McKenney
2005-01-07 7:33 ` Arjan van de Ven
2005-01-07 8:15 ` Christoph Hellwig
2005-01-07 15:12 ` Paul E. McKenney
2005-01-07 15:23 ` Arjan van de Ven
2005-01-07 15:34 ` Paul E. McKenney
2005-01-07 15:56 ` Arjan van de Ven
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=20050107233246.GH14108@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=greghk@us.ibm.com \
--cc=hch@infradead.org \
--cc=jtk@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markv@us.ibm.com \
--cc=mingo@elte.hu \
--cc=paulmck@us.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=wtaber@us.ibm.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
Powered by JetHome