Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759470AbXLOGBp (ORCPT ); Sat, 15 Dec 2007 01:01:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752252AbXLOGBi (ORCPT ); Sat, 15 Dec 2007 01:01:38 -0500 Received: from smtp2.linux-foundation.org ([207.189.120.14]:58642 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751741AbXLOGBh (ORCPT ); Sat, 15 Dec 2007 01:01:37 -0500 Date: Fri, 14 Dec 2007 22:00:30 -0800 From: Andrew Morton To: Dhaval Giani Cc: htejun@gmail.com, gregkh@suse.de, stable@kernel.org, linux-kernel@vger.kernel.org, maneesh@linux.vnet.ibm.com, vatsa@linux.vnet.ibm.com, balbir@in.ibm.com, ego@in.ibm.com, linux-mm@kvack.org Subject: Re: 2.6.22-stable causes oomkiller to be invoked Message-Id: <20071214220030.325f82b8.akpm@linux-foundation.org> In-Reply-To: <20071215035200.GA22082@linux.vnet.ibm.com> References: <20071213162936.GA7635@suse.de> <20071213164658.GA30865@linux.vnet.ibm.com> <20071213175423.GA2977@linux.vnet.ibm.com> <476295FF.1040202@gmail.com> <20071214154711.GD23670@linux.vnet.ibm.com> <4762A721.7080400@gmail.com> <20071214161637.GA2687@linux.vnet.ibm.com> <20071214095023.b5327703.akpm@linux-foundation.org> <20071214182802.GC2576@linux.vnet.ibm.com> <20071214150533.aa30efd4.akpm@linux-foundation.org> <20071215035200.GA22082@linux.vnet.ibm.com> X-Mailer: Sylpheed 2.4.1 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1870 Lines: 56 On Sat, 15 Dec 2007 09:22:00 +0530 Dhaval Giani wrote: > > Is it really the case that the bug only turns up when you run tests like > > > > while echo; do cat /sys/kernel/kexec_crash_loaded; done > > and > > while echo; do cat /sys/kernel/uevent_seqnum ; done; > > > > or will any fork-intensive workload also do it? Say, > > > > while echo ; do true ; done > > > > This does not leak, but having a simple text file and reading it in a > loop causes it. hm. > > ? > > > > Another interesting factoid here is that after the oomkilling you slabinfo has > > > > mm_struct 38 98 584 7 1 : tunables 32 16 8 : slabdata 14 14 0 : globalstat 2781 196 49 31 0 1 0 0 0 : cpustat 368800 11864 368920 11721 > > > > so we aren't leaking mm_structs. In fact we aren't leaking anything from > > slab. But we are leaking pgds. > > > > iirc the most recent change we've made in the pgd_t area is the quicklist > > management which went into 2.6.22-rc1. You say the bug was present in > > 2.6.22. Can you test 2.6.21? > > Nope, leak is not present in 2.6.21.7 Could you try this debug patch please? It might need some fiddling to get useful output. Basic idea is to see if we are failing to empty the quicklists. --- a/include/linux/quicklist.h~a +++ a/include/linux/quicklist.h @@ -69,6 +69,8 @@ static inline void __quicklist_free(int *(void **)p = q->page; q->page = p; q->nr_pages++; + if (q->nr_pages && !(q->nr_pages % 1000)) + printk("eek: %d\n", q->nr_pages); put_cpu_var(quicklist); } _ -- 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/