[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AD6EF65.6080602@cn.fujitsu.com>
Date: Thu, 15 Oct 2009 17:46:13 +0800
From: Li Zefan <lizf@...fujitsu.com>
To: Zdenek Kabelac <zdenek.kabelac@...il.com>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Catalin Marinas <catalin.marinas@....com>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: Leaks in trace reported by kmemleak
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..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists