From: Tvrtko Ursulin Subject: Re: 2.6.33.2 kmalloc-8 slab leaks ~512 objects per second Date: Thu, 13 May 2010 13:39:31 +0100 Message-ID: <201005131339.32113.tvrtko.ursulin@sophos.com> References: <201005121121.49135.tvrtko.ursulin@sophos.com> <201005121404.49720.tvrtko.ursulin@sophos.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Catalin Marinas Cc: Pekka Enberg , "linux-kernel@vger.kernel.org" , Andrew Morton , David Airlie , "dri-devel@lists.sourceforge.net" , Jerome Glisse List-Id: dri-devel@lists.freedesktop.org On Thursday 13 May 2010 13:29:49 Catalin Marinas wrote: > Tvrtko Ursulin wrote: > > On Wednesday 12 May 2010 14:00:51 Pekka Enberg wrote: > >> [snip] > >> > >> You might want to try out the built-in kernel memory leak detector. > >> See Documentation/kmemleak.txt for details how to enable it and use > >> it. > > > > Thanks for the suggestion, I will have to try it out once but not this > > time :) because 2.6.34-rc7 seems to be fine, or in other words not > > leaking. > > You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs > and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so. I could do it if radeon/drm guys would be interested in those results? (Given how 2.6.34-rc7 is not leaking.) Tvrtko Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20.