Prev: vhost: fix barrier pairing
Next: [PATCH] rwsem: Test for no active locks in __rwsem_do_wake undo code
From: Tvrtko Ursulin on 26 May 2010 12:30
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2 3
Prev: vhost: fix barrier pairing
Next: [PATCH] rwsem: Test for no active locks in __rwsem_do_wake undo code