[PATCH 0/4] prepare for ->siglock safe threads traversal

From: Oleg Nesterov
Date: Mon Feb 20 2006 - 09:44:12 EST


The main problem is that copy_process's error path and
release_task() share __exit_signal() which locks ->sighand
and destroys it, but we need to do __unhash_process() under
->sighand.

This patch series tries to solves this. It also tries to
simplify and cleanup the code a bit.

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