From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx113.postini.com [74.125.245.113]) by kanga.kvack.org (Postfix) with SMTP id 2319C6B0068 for ; Wed, 11 Jan 2012 22:48:58 -0500 (EST) Received: by mail-qy0-f169.google.com with SMTP id d17so965582qcs.14 for ; Wed, 11 Jan 2012 19:48:57 -0800 (PST) Message-ID: <4F0E5827.7090603@gmail.com> Date: Wed, 11 Jan 2012 22:48:55 -0500 From: KOSAKI Motohiro MIME-Version: 1.0 Subject: Re: [patch 3/3] mm, oom: do not emit oom killer warning if chosen thread is already exiting References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: David Rientjes Cc: Andrew Morton , KAMEZAWA Hiroyuki , KOSAKI Motohiro , linux-mm@kvack.org (1/11/12 10:24 PM), David Rientjes wrote: > If a thread is chosen for oom kill and is already PF_EXITING, then the > oom killer simply sets TIF_MEMDIE and returns. This allows the thread to > have access to memory reserves so that it may quickly exit. This logic > is preceeded with a comment saying there's no need to alarm the sysadmin. > This patch adds truth to that statement. > > There's no need to emit any warning about the oom condition if the thread > is already exiting since it will not be killed. In this condition, just > silently return the oom killer since its only giving access to memory > reserves and is otherwise a no-op. > > Signed-off-by: David Rientjes > --- Acked-by: KOSAKI Motohiro -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org