From: Catalin Marinas <catalin.marinas@arm.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Dave Airlie <airlied@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
airlied@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Eric Anholt <eric@anholt.net>
Subject: Re: Memory leak issues in drm
Date: Thu, 16 Jul 2009 09:44:48 +0100 [thread overview]
Message-ID: <1247733888.24965.3.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <1247728158.2543.4.camel@ht.satnam>
On Thu, 2009-07-16 at 12:39 +0530, Jaswinder Singh Rajput wrote:
> On Thu, 2009-07-16 at 10:37 +0530, Jaswinder Singh Rajput wrote:
> > On linus tree, while investigating kmemleak issues in drm :
> >
> > unreferenced object 0xf571dea0 (size 32):
> > comm "Xorg", pid 1992, jiffies 4294703188
> > backtrace:
> > [<c1096655>] create_object+0x140/0x210
> > [<c10967f2>] kmemleak_alloc+0x25/0x4b
> > [<c1093b63>] __kmalloc+0xcb/0x153
> > [<c11ae939>] drm_setversion+0x154/0x1f6
> > [<c11ad0b1>] drm_ioctl+0x211/0x296
> > [<c10a2dc9>] vfs_ioctl+0x50/0x69
> > [<c10a3321>] do_vfs_ioctl+0x49b/0x4d5
> > [<c10a3387>] sys_ioctl+0x2c/0x45
> > [<c1002988>] sysenter_do_call+0x12/0x36
> > [<ffffffff>] 0xffffffff
> >
>
> This fixes above memory leak in drm because it was allocating again on
> dev->devname without freeing previous instance and more memory related
> issues, hope this will be helpful:
Thanks for looking into this (I haven't tried the patch yet but it seems
that you found the cause of the leak).
In case you have time, I reported this as well and another in the drm
code - http://lkml.org/lkml/2009/7/9/110 - which happens when a graphics
application exits.
--
Catalin
next prev parent reply other threads:[~2009-07-16 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 5:07 Memory leak issues in drm Jaswinder Singh Rajput
2009-07-16 7:09 ` Jaswinder Singh Rajput
2009-07-16 8:44 ` Catalin Marinas [this message]
2009-07-23 0:02 ` Andrew Morton
2009-07-23 2:15 ` Dave Airlie
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=1247733888.24965.3.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eric@anholt.net \
--cc=jaswinder@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