From: Li Zefan <lizf@cn.fujitsu.com>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Leaks in trace reported by kmemleak
Date: Thu, 15 Oct 2009 17:46:13 +0800 [thread overview]
Message-ID: <4AD6EF65.6080602@cn.fujitsu.com> (raw)
In-Reply-To: <c4e36d110910150159j6092d0d1lb20434bd9d43d8ce@mail.gmail.com>
CC: ...
Zdenek Kabelac wrote:
> I've noticed your latest patch for memory leak in filter setting
> (8ad807318fcd...) - but even with this patch - kmemleak seems to still
> report lots (~900) of following leaks - note - they come only from
> i915 and kvm module - so I'm not sure if these two modules are doing
> something wrong or the problem is in trace code.
>
> It looks like whole directory is somehow forgotten.
>
Fortunately those are false-positives:
# modprobe i915
# echo scan > /debug/kmemleak
# cat /debug/kmemleak
(lots of "leaks")
# rmmod i915
# echo scan > /debug/kmemleak
# cat /debug/kmemleak
(no leaks)
All the memory allocated when loading the module is
freed in trace_module_remove_events() at module unload.
But I haven't looked into how to suppress those false-postives.
I'd like to, but I'm going to leave my office and won't be
back until 26th..
next prev parent reply other threads:[~2009-10-15 9:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 8:59 Leaks in trace reported by kmemleak Zdenek Kabelac
2009-10-15 9:46 ` Li Zefan [this message]
2009-10-15 11:22 ` Catalin Marinas
2009-10-16 7:45 ` Zdenek Kabelac
2009-10-16 10:57 ` Catalin Marinas
2009-10-16 13:32 ` Zdenek Kabelac
2009-10-16 14:11 ` Catalin Marinas
2009-10-16 14:28 ` Zdenek Kabelac
2009-10-16 15:07 ` Zdenek Kabelac
2009-10-16 15:31 ` Catalin Marinas
2009-10-16 16:41 ` Catalin Marinas
2009-10-19 9:15 ` Zdenek Kabelac
2009-10-19 12:00 ` Catalin Marinas
2009-10-19 13:20 ` Catalin Marinas
2009-10-20 9:58 ` Zdenek Kabelac
2009-10-20 17:03 ` Catalin Marinas
2009-10-22 13:09 ` Catalin Marinas
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=4AD6EF65.6080602@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=catalin.marinas@arm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=zdenek.kabelac@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.