From: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
To: David Rientjes <rientjes@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Airlie <airlied@linux.ie>,
"dri-devel@lists.sourceforge.net"
<dri-devel@lists.sourceforge.net>,
Jerome Glisse <glisse@freedesktop.org>
Subject: Re: 2.6.33.2 kmalloc-8 slab leaks ~512 objects per second
Date: Wed, 26 May 2010 17:22:14 +0100 [thread overview]
Message-ID: <201005261722.14252.tvrtko.ursulin@sophos.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005260220460.8417@chino.kir.corp.google.com>
On Wednesday 26 May 2010 10:21:36 David Rientjes wrote:
> On Thu, 13 May 2010, Tvrtko Ursulin wrote:
> > > 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.)
>
> Did you get a chance to find out if kmemleak was able to identify the
> source of this problem?
Well no, I asked DRM/radeon guys to explicitly say whether it would be useful,
otherwise it is unfortunately sufficiently low on my priority list that it
will probably never happen.
Tvrtko
Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
next prev parent reply other threads:[~2010-05-26 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 10:21 Tvrtko Ursulin
2010-05-12 13:00 ` Pekka Enberg
2010-05-12 13:04 ` Tvrtko Ursulin
2010-05-13 12:29 ` Catalin Marinas
2010-05-13 12:39 ` Tvrtko Ursulin
2010-05-26 9:21 ` David Rientjes
2010-05-26 16:22 ` Tvrtko Ursulin [this message]
[not found] <11758_1273660249_4BEA8359_11758_1675_1_201005121121.49135.tvrtko.ursulin@sophos.com>
2010-05-12 10:38 ` Tvrtko Ursulin
2010-05-12 10:50 ` Tvrtko Ursulin
2010-05-12 13:29 ` Jerome Glisse
2010-05-12 13:37 ` Tvrtko Ursulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201005261722.14252.tvrtko.ursulin@sophos.com \
--to=tvrtko.ursulin@sophos.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=glisse@freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®