From: Catalin Marinas <catalin.marinas@arm.com>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: "kernel-testers-owner@vger.kernel.org"
<kernel-testers-owner@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: possible memory leak on i915_gem_create_ioctl
Date: Tue, 14 Jul 2009 15:28:20 +0100 [thread overview]
Message-ID: <1247581700.28240.106.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <4A5C93AD.5050403@fisher-privat.net>
On Tue, 2009-07-14 at 16:18 +0200, Alexey Fisher wrote:
> kmemleak report a lot of possible memory leaks if using any glxrelated
> applications like glxgears, glxinfo, compiz, cairo-dock with g45 graphic.
>
> Here is a trace from /sys/kernel/debug/kmemleak:
>
> unreferenced object 0xffff8800b298e000 (size 544):
> comm "openarena", pid 5002, jiffies 4296480664
> backtrace:
> [<ffffffff814ac755>] kmemleak_alloc+0x25/0x60
> [<ffffffff810f4b8b>] kmem_cache_alloc+0xfb/0x180
> [<ffffffff8122404f>] idr_pre_get+0x5f/0x90
> [<ffffffff812c6fed>] drm_gem_handle_create+0x2d/0xa0
> [<ffffffff812e0d60>] i915_gem_create_ioctl+0x60/0xc0
> [<ffffffff812c5c74>] drm_ioctl+0x184/0x3b0
> [<ffffffff8110c6dc>] vfs_ioctl+0x7c/0xa0
> [<ffffffff8110cbaa>] do_vfs_ioctl+0x8a/0x5a0
> [<ffffffff8110d141>] sys_ioctl+0x81/0xa0
> [<ffffffff8100b66b>] system_call_fastpath+0x16/0x1b
> [<ffffffffffffffff>] 0xffffffffffffffff
I already reported these - http://lkml.org/lkml/2009/7/9/110.
They look like real leaks but someone who understands the code better
would need to look at them.
--
Catalin
prev parent reply other threads:[~2009-07-14 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 14:18 Alexey Fisher
2009-07-14 14:28 ` Catalin Marinas [this message]
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=1247581700.28240.106.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=bug-track@fisher-privat.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel-testers-owner@vger.kernel.org \
--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®