From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with SMTP id 093636B01E1 for ; Tue, 8 Jun 2010 16:27:38 -0400 (EDT) Date: Tue, 8 Jun 2010 22:26:11 +0200 From: Oleg Nesterov Subject: Re: [patch 06/18] oom: avoid sending exiting tasks a SIGKILL Message-ID: <20100608202611.GA11284@redhat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: David Rientjes Cc: Andrew Morton , Rik van Riel , Nick Piggin , Balbir Singh , KAMEZAWA Hiroyuki , KOSAKI Motohiro , linux-mm@kvack.org List-ID: To clarify, I am not going to review this patch ;) As I said many times I can only understand what oom_kill.c does, but now why. On 06/06, David Rientjes wrote: > > It's unnecessary to SIGKILL a task that is already PF_EXITING This probably needs some explanation. PF_EXITING doesn't necessarily mean this process is exiting. > and can > actually cause a NULL pointer dereference of the sighand Yes. Another reason to avoid force_sig(). Oleg. -- 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