Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755654Ab2FJCPs (ORCPT ); Sat, 9 Jun 2012 22:15:48 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:55639 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753936Ab2FJCPr (ORCPT ); Sat, 9 Jun 2012 22:15:47 -0400 Date: Sat, 9 Jun 2012 19:15:45 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Thomas Gleixner cc: Dave Jones , Linux Kernel , linux-mm@kvack.org Subject: Re: oomkillers gone wild. In-Reply-To: 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: 869 Lines: 19 On Fri, 8 Jun 2012, Thomas Gleixner wrote: > > 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. > > I rather suspect, that this is a asymetry between get_ and > put_task_struct and refcount just doesn't go to zero. > We found an actual task_struct leak within put_task_struct() because of the free task notifiers during the 3.4 -rc cycle, so if kmemleak doesn't show anything then would it be possible to bisect the problem Dave? -- 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/