I'm running a customized 2.6.10 and seeing some interesting behaviour.
Based on some additional debugging that we added, the "p->signal" member
is being set to NULL between the time we call spin_lock() and the time
we return from it.
Anyone have any ideas what might be going on? It seems to go away if we
boot with only 1 cpu. I assume that some other cpu already holds that
lock and does something while holding it that causes the "p->signal"
member to become NULL.
void release_task(struct task_struct * p)
struct dentry *proc_dentry;
proc_dentry = proc_pid_unhash(p);
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Video 4 Linux]
[Linux for the blind]