From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932732Ab2JWJIo (ORCPT ); Tue, 23 Oct 2012 05:08:44 -0400 Received: from mail-vc0-f174.google.com ([209.85.220.174]:43705 "EHLO mail-vc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756666Ab2JWJIm (ORCPT ); Tue, 23 Oct 2012 05:08:42 -0400 MIME-Version: 1.0 In-Reply-To: <20121023083556.GB15397@dhcp22.suse.cz> References: <20121019160425.GA10175@dhcp22.suse.cz> <20121023083556.GB15397@dhcp22.suse.cz> Date: Tue, 23 Oct 2012 17:08:40 +0800 Message-ID: Subject: Re: process hangs on do_exit when oom happens From: Qiang Gao To: Michal Hocko Cc: "linux-kernel@vger.kernel.org" , "linux-mmc@vger.kernel.org" , "cgroups@vger.kernel.org" , linux-mm@kvack.org, bsingharora@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org this is just an example to show how to reproduce. actually,the first time I saw this situation was on a machine with 288G RAM with many tasks running and we limit 30G for each. but finanlly, no one exceeds this limit the the system oom. On Tue, Oct 23, 2012 at 4:35 PM, Michal Hocko wrote: > On Tue 23-10-12 11:35:52, Qiang Gao wrote: >> I'm sure this is a global-oom,not cgroup-oom. [the dmesg output in the end] > > Yes this is the global oom killer because: >> cglimit -M 700M ./tt >> then after global-oom,the process hangs.. > >> 179184 pages RAM > > So you have ~700M of RAM so the memcg limit is basically pointless as it > cannot be reached... > -- > Michal Hocko > SUSE Labs