Re: [PATCH] de_thread: eliminate unneccessary sighand locking

[Roland McGrath <roland@redhat.com>]

> while switching current->sighand de_thread does:
> 
> 	write_lock_irq(&tasklist_lock);
> 	spin_lock(&oldsighand->siglock);
> 	spin_lock(&newsighand->siglock);
> 
> 	current->sighand = newsighand;
> 	recalc_sigpending();
> 
> Is these 2 sighand locks are really needed?

Yes.  Other processes can do spin_lock_irq(&ourtask->sighand->siglock);
without holding tasklist_lock.  If someone just did that, they hold
oldsighand->siglock but no newsighand->siglock, and may then be about to
look at ourtask->sighand.  By holding oldsighand->siglock, we ensure that
we can't be colliding with anything like that.  

> The only possibility that I can imagine is that some process
> does:
> 	read_lock(tasklist_lock);
> 	task = find_task();
> 	spin_lock(task->sighand->siglock);
> 	read_unlock(tasklist_lock);
> 	play with task->signal
> 
> Is this possible/allowed?

Yes.

> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>

NAK from me.


Thanks,
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/