Date: Tue, 24 Sep 2013 19:34:54 -0700 (PDT)
From: David Rientjes <rientjes@google.com>
To: Ming Liu <ming.liu@windriver.com>
cc: akpm@linux-foundation.org, mhocko@suse.cz, rusty@rustcorp.com.au,
        hannes@cmpxchg.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] oom: avoid killing init if it assume the oom killed
 thread's mm
In-Reply-To: <1379929528-19179-1-git-send-email-ming.liu@windriver.com>
Message-ID: <alpine.DEB.2.02.1309241933590.26187@chino.kir.corp.google.com>
References: <1379929528-19179-1-git-send-email-ming.liu@windriver.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 870
Lines: 19

On Mon, 23 Sep 2013, Ming Liu wrote:

> After selecting a task to kill, the oom killer iterates all processes and
> kills all other user threads that share the same mm_struct in different
> thread groups.
> 
> But in some extreme cases, the selected task happens to be a vfork child
> of init process sharing the same mm_struct with it, which causes kernel
> panic on init getting killed. This panic is observed in a busybox shell
> that busybox itself is init, with a kthread keeps consuming memories.
> 

We shouldn't be selecting a process where mm == init_mm in the first 
place, so this wouldn't fix the issue entirely.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/