Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934422Ab2FHT5k (ORCPT ); Fri, 8 Jun 2012 15:57:40 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:51593 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933436Ab2FHT5j (ORCPT ); Fri, 8 Jun 2012 15:57:39 -0400 Date: Fri, 8 Jun 2012 12:57:36 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Dave Jones , Linux Kernel , linux-mm@kvack.org Subject: Re: oomkillers gone wild. In-Reply-To: <20120605185239.GA28172@redhat.com> Message-ID: References: <20120604152710.GA1710@redhat.com> <20120605174454.GA23867@redhat.com> <20120605185239.GA28172@redhat.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1497 Lines: 38 On Tue, 5 Jun 2012, Dave Jones wrote: > OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME > 142524 142420 99% 9.67K 47510 3 1520320K task_struct > 142560 142417 99% 1.75K 7920 18 253440K signal_cache > 142428 142302 99% 1.19K 5478 26 175296K task_xstate > 306064 289292 94% 0.36K 6956 44 111296K debug_objects_cache > 143488 143306 99% 0.50K 4484 32 71744K cred_jar > 142560 142421 99% 0.50K 4455 32 71280K task_delay_info > 150753 145021 96% 0.45K 4308 35 68928K kmalloc-128 > > Why so many task_structs ? There's only 128 processes running, and most of them > are kernel threads. > Do you have CONFIG_OPROFILE enabled? > /sys/kernel/slab/task_struct/alloc_calls shows.. > > 142421 copy_process.part.21+0xbb/0x1790 age=8/19929576/48173720 pid=0-16867 cpus=0-7 > > I get the impression that the oom-killer hasn't cleaned up properly after killing some of > those forked processes. > > any thoughts ? > If we're leaking task_struct's, meaning that put_task_struct() isn't actually freeing them when the refcount goes to 0, then it's certainly not because of the oom killer which only sends a SIGKILL to the selected process. Have you tried kmemleak? -- 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/