[PATCH] signal, procfs: some lock_task_sighand() users do not need rcu_read_lock()
authorLai Jiangshan <laijs@cn.fujitsu.com>
Sat, 4 Oct 2008 20:51:15 +0000 (00:51 +0400)
committerAlexey Dobriyan <adobriyan@gmail.com>
Fri, 10 Oct 2008 00:18:57 +0000 (04:18 +0400)
commita6bebbc87a8c16eabb6bd5c6fd2d994be0236fba
tree3e617ca49063f3a12c982da5d6c687882a1b4070
parent53167a3ef23df561d898dee636f3393e9fba937c
[PATCH] signal, procfs: some lock_task_sighand() users do not need rcu_read_lock()

lock_task_sighand() make sure task->sighand is being protected,
so we do not need rcu_read_lock().
[ exec() will get task->sighand->siglock before change task->sighand! ]

But code using rcu_read_lock() _just_ to protect lock_task_sighand()
only appear in procfs. (and some code in procfs use lock_task_sighand()
without such redundant protection.)

Other subsystem may put lock_task_sighand() into rcu_read_lock()
critical region, but these rcu_read_lock() are used for protecting
"for_each_process()", "find_task_by_vpid()" etc. , not for protecting
lock_task_sighand().

Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
[ok from Oleg]
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
fs/proc/array.c
fs/proc/base.c
kernel/sched_debug.c