[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201005131339.32113.tvrtko.ursulin@sophos.com>
Date: Thu, 13 May 2010 13:39:31 +0100
From: Tvrtko Ursulin <tvrtko.ursulin@...hos.com>
To: Catalin Marinas <catalin.marinas@....com>
CC: Pekka Enberg <penberg@...helsinki.fi>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Airlie <airlied@...ux.ie>,
"dri-devel@...ts.sourceforge.net" <dri-devel@...ts.sourceforge.net>,
Jerome Glisse <glisse@...edesktop.org>
Subject: Re: 2.6.33.2 kmalloc-8 slab leaks ~512 objects per second
On Thursday 13 May 2010 13:29:49 Catalin Marinas wrote:
> Tvrtko Ursulin <tvrtko.ursulin@...hos.com> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists