From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx125.postini.com [74.125.245.125]) by kanga.kvack.org (Postfix) with SMTP id 861DA6B0062 for ; Wed, 31 Oct 2012 14:42:31 -0400 (EDT) Received: by mail-pa0-f41.google.com with SMTP id fa10so1295219pad.14 for ; Wed, 31 Oct 2012 11:42:30 -0700 (PDT) Date: Wed, 31 Oct 2012 11:42:28 -0700 (PDT) From: David Rientjes Subject: Re: zram OOM behavior In-Reply-To: Message-ID: References: <20121015144412.GA2173@barrios> <20121016061854.GB3934@barrios> <20121022235321.GK13817@bbox> <20121030001809.GL15767@bbox> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Luigi Semenzato Cc: Minchan Kim , linux-mm@kvack.org, Dan Magenheimer , KOSAKI Motohiro , Sonny Rao On Tue, 30 Oct 2012, Luigi Semenzato wrote: > For completeness, I would like to report that the page fault in > mm_release looks legitimate. The fault happens near here: > > if (unlikely(tsk->robust_list)) { > exit_robust_list(tsk); > tsk->robust_list = NULL; > } > > and robust_list is a userspace structure. > This is the only place where the hang occurs when there are several threads in the exit path with PF_EXITING and it causes the oom killer to defer killing a process? If that's the case, then a simple tsk->robust_list check would be sufficient to avoid deferring incorrectly. -- 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: email@kvack.org