Re: [patch] oom: print triggering task's cpuset and mems allowed

[David Rientjes]

On Wed, 19 Nov 2008, Li Zefan wrote:

> But none of the callers of this function holds task_lock nor rcu_read_lock,
> they hold tasklist_lock. Have you confirmed this is ok? It seems racy that
> the task may be moved to another cgroup and the original cgroup gets removed.
> 

It needs task_lock(current).
--
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/