Re: zram OOM behavior

On Mon, 29 Oct 2012, Luigi Semenzato wrote:

However, now there is something that worries me more.  The trace of
the thread with TIF_MEMDIE set shows that it has executed most of
do_exit() and appears to be waiting to be reaped.  From my reading of
the code, this implies that task->exit_state should be non-zero, which
means that select_bad_process should have skipped that thread, which
means that we cannot be in the deadlock situation, and my experiments
are not consistent.

Yeah, this is what I was referring to earlier, select_bad_process() will 
not consider the thread for which you posted a stack trace for oom kill, 
so it's not deferring because of it.  There are either other thread(s) 
that have been oom killed and have not yet release their memory or the oom 
killer is never being called.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>