aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/feature-removal-schedule.txt
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2006-03-24 06:18:33 -0500
committerLinus Torvalds <torvalds@g5.osdl.org>2006-03-24 10:33:29 -0500
commitde62a97ef576a1f6b5013139ded9893226375bbb (patch)
tree39589587c7c48b4d2e3f1dc6a1c8ddb863ce814c /Documentation/feature-removal-schedule.txt
parent554b7c801e379e8c0072533b4da89a3a003cbfac (diff)
[PATCH] deprecate the tasklist_lock export
Drivers have no business looking at the task list and thus using this lock. The only possibly modular users left are: arch/ia64/kernel/mca.c drivers/edac/edac_mc.c fs/binfmt_elf.c which I'll send out fixes for soon. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/feature-removal-schedule.txt')
-rw-r--r--Documentation/feature-removal-schedule.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 803a9edb7cd7..21272e4b4a5c 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -185,6 +185,17 @@ Who: Jean Delvare <khali@linux-fr.org>
185 185
186--------------------------- 186---------------------------
187 187
188What: remove EXPORT_SYMBOL(tasklist_lock)
189When: August 2006
190Files: kernel/fork.c
191Why: tasklist_lock protects the kernel internal task list. Modules have
192 no business looking at it, and all instances in drivers have been due
193 to use of too-lowlevel APIs. Having this symbol exported prevents
194 moving to more scalable locking schemes for the task list.
195Who: Christoph Hellwig <hch@lst.de>
196
197---------------------------
198
188What: mount/umount uevents 199What: mount/umount uevents
189When: February 2007 200When: February 2007
190Why: These events are not correct, and do not properly let userspace know 201Why: These events are not correct, and do not properly let userspace know