From: Catalin Marinas <catalin.marinas@arm.com>
To: David Airlie <airlied@linux.ie>, dri-devel@lists.sourceforge.net
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Possible memory leaks in drivers/gpu/drm/
Date: Thu, 09 Jul 2009 10:47:10 +0100 [thread overview]
Message-ID: <1247132830.11409.29.camel@pc1117.cambridge.arm.com> (raw)
Hi,
I get some kmemleak reports in the drm code. The first happens when Xorg
is running:
unreferenced object 0xc2659050 (size 32):
comm "Xorg", pid 2585, jiffies 4294902558
backtrace:
[<c01e0c3a>] create_object+0xfa/0x250
[<c01e1e7d>] kmemleak_alloc+0x5d/0x70
[<c01db2d5>] __kmalloc+0x115/0x1f0
[<fa3a53f5>] drm_setversion+0x1c5/0x260 [drm]
[<fa3a3612>] drm_ioctl+0x192/0x3a0 [drm]
[<c01f1d29>] vfs_ioctl+0x79/0x90
[<c01f1e8a>] do_vfs_ioctl+0x6a/0x5e0
[<c01f2463>] sys_ioctl+0x63/0x70
[<c010300c>] sysenter_do_call+0x12/0x38
It looks like this is one of the kmalloc calls in the drm_set_busid()
function (I'll do more checks tonight to see exactly which of the two
kmalloc's).
When the Xorg exits, it seems to leave behind several of these (the same
happens when glxinfo exits):
unreferenced object 0xc22b7540 (size 148):
comm "Xorg", pid 2585, jiffies 4294902559
backtrace:
[<c01e0c3a>] create_object+0xfa/0x250
[<c01e1e7d>] kmemleak_alloc+0x5d/0x70
[<c01dac1b>] kmem_cache_alloc+0x14b/0x190
[<c0309400>] idr_pre_get+0x50/0x70
[<fa3a4d74>] drm_gem_handle_create+0x24/0x90 [drm]
[<fa7f79ad>] i915_gem_create_ioctl+0x5d/0xb0 [i915]
[<fa3a3612>] drm_ioctl+0x192/0x3a0 [drm]
[<c01f1d29>] vfs_ioctl+0x79/0x90
[<c01f1e8a>] do_vfs_ioctl+0x6a/0x5e0
[<c01f2463>] sys_ioctl+0x63/0x70
[<c010300c>] sysenter_do_call+0x12/0x38
Are they real leaks?
Thanks.
--
Catalin
reply other threads:[~2009-07-09 9:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1247132830.11409.29.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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®