kmemleak and drm/i915 - linux 2.6.31-rc4

From: ããããããã
Date: Sat Aug 01 2009 - 07:51:54 EST


Hello,

Trying to identify another problem, I found this one : any GL application
that is started on my machine ends adding a new entry like this one in the
kmemleak detector :

unreferenced object 0xffff880079bf9760 (size 544):
comm "glslideshow", pid 17138, jiffies 4304401728
backtrace:
[<ffffffff810a7f4c>] create_object+0x186/0x287
[<ffffffff810a8130>] kmemleak_alloc+0x21/0x45
[<ffffffff810a3c45>] kmem_cache_alloc+0xad/0xbf
[<ffffffff8118b441>] idr_pre_get+0x2d/0x6f
[<ffffffff81212483>] drm_gem_handle_create+0x26/0x7a
[<ffffffff8122bd33>] i915_gem_create_ioctl+0x55/0xa6
[<ffffffff81210f51>] drm_ioctl+0x223/0x2c9
[<ffffffff810b6316>] vfs_ioctl+0x6a/0x82
[<ffffffff810b6818>] do_vfs_ioctl+0x473/0x4b9
[<ffffffff810b68af>] sys_ioctl+0x51/0x74
[<ffffffff8100b9eb>] system_call_fastpath+0x16/0x1b
[<ffffffffffffffff>] 0xffffffffffffffff

This can be easily reproduced by starting glxgears for example.

Regards,
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/