From: Christoph Hellwig <hch@lst.de>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] deprecate the tasklist_lock export
Date: Wed, 15 Feb 2006 14:07:34 +0100 [thread overview]
Message-ID: <20060215130734.GA5590@lst.de> (raw)
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>
Index: linux-2.6/Documentation/feature-removal-schedule.txt
===================================================================
--- linux-2.6.orig/Documentation/feature-removal-schedule.txt 2006-02-15 14:03:37.000000000 +0100
+++ linux-2.6/Documentation/feature-removal-schedule.txt 2006-02-15 14:05:37.000000000 +0100
@@ -182,3 +182,14 @@
implementation details and provides a higherlevel interface that
prevents bugs and code duplication
Who: Christoph Hellwig <hch@lst.de>
+
+---------------------------
+
+What: remove EXPORT_SYMBOL(tasklist_lock)
+When: August 2006
+Files: kernel/fork.c
+Why: tasklist_lock protects the kernel internal task list. Modules have
+ no business looking at it, and all instances in drivers have been due
+ to use of too-lowlevel APIs. Having this symbol exported prevents
+ moving to more scalable locking schemes for the task list.
+Who: Christoph Hellwig <hch@lst.de>
next reply other threads:[~2006-02-15 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 13:07 Christoph Hellwig [this message]
2006-02-15 14:09 ` [PATCH] deprecate the tasklist_lock export Steven Rostedt
2006-02-17 11:20 ` Christoph Hellwig
2006-02-17 12:31 ` Steven Rostedt
2006-02-15 21:48 ` Adrian Bunk
2006-02-17 11:23 ` Christoph Hellwig
2006-02-17 20:12 ` Adrian Bunk
2006-02-16 20:50 ` Olaf Titz
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=20060215130734.GA5590@lst.de \
--to=hch@lst.de \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.