From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with SMTP id E9CDF6B0220 for ; Thu, 3 Jun 2010 10:05:33 -0400 (EDT) Date: Thu, 3 Jun 2010 16:03:57 +0200 From: Oleg Nesterov Subject: Re: [PATCH] oom: Make coredump interruptible Message-ID: <20100603140357.GB3548@redhat.com> References: <20100601093951.2430.A69D9226@jp.fujitsu.com> <20100601201843.GA20732@redhat.com> <20100602221805.F524.A69D9226@jp.fujitsu.com> <20100602154210.GA9622@redhat.com> <20100602172956.5A3E34A491@magilla.sf.frob.com> <20100602175325.GA16474@redhat.com> <20100602185812.4B5894A549@magilla.sf.frob.com> <20100602203827.GA29244@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100602203827.GA29244@redhat.com> Sender: owner-linux-mm@kvack.org To: Roland McGrath Cc: KOSAKI Motohiro , LKML , linux-mm , David Rientjes , Andrew Morton , KAMEZAWA Hiroyuki , Nick Piggin List-ID: On 06/02, Oleg Nesterov wrote: > > On 06/02, Roland McGrath wrote: > > > > > when select_bad_process() finds the task P to kill it can participate > > > in the core dump (sleep in exit_mm), but we should somehow inform the > > > thread which actually dumps the core: P->mm->core_state->dumper. > > > > Perhaps it should simply do that: if you would choose P to oom-kill, and > > P->mm->core_state!=NULL, then choose P->mm->core_state->dumper instead. > > ... to set TIF_MEMDIE which should be checked in elf_core_dump(). > > Probably yes. Well, nothing can protect mm->core_state, the dumper owns it. Of course we can add the locking, but this is not nice. And again, perhaps MMF_OOMKILLED can be useful anyway. So, I think this would be the most quick/simple fix for now. 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