From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Sankar P <sankar.curiosity@gmail.com>
Cc: "rnagarajan@novell.com" <rnagarajan@novell.com>,
"teheo@novell.com" <teheo@novell.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Probable Bug (or configuration error) in kmemleak
Date: Thu, 17 Jun 2010 10:36:04 -0700 [thread overview]
Message-ID: <20100617173604.GB28055@tux> (raw)
In-Reply-To: <AANLkTikaH5sYv-pa6OEIPCofF8RAbi7F3nTdWqEXWr8J@mail.gmail.com>
On Thu, Jun 17, 2010 at 02:21:56AM -0700, Sankar P wrote:
> Hi,
>
> I wanted to detect memory leaks in one of my kernel modules. So I
> built Linus' tree with the following config options enabled (on top
> of make defconfig)
>
> CONFIG_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=400
> CONFIG_DEBUG_KMEMLEAK_TEST=y
>
> If I boot with this kernel, debugfs is automatically mounted. But I do
> not have the file:
>
> /sys/kernel/debug/kmemleak
>
> created at all. There are other files like kprobes in the mounted
> /sys/kernel/debug directory btw. So I am not able to detect any of the
> memory leaks. Is there anything I am doing wrong or missing (or) is
> this a bug in kmemleak ?
>
> Please let me know your suggestions to fix this and get memory leaks
> reporting working. Thanks.
>
> The full .config file is also attached with this mail. Sorry for the
> attachment, I did not want to paste 5k lines in the mail. Sorry if it
> is wrong.
This is odd.. Do you see this message on your kernel ring buffer?
Failed to create the debugfs kmemleak file
Luis
next prev parent reply other threads:[~2010-06-17 17:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 9:21 Probable Bug (or configuration error) in kmemleak Sankar P
2010-06-17 17:36 ` Luis R. Rodriguez [this message]
2010-06-18 8:11 ` Sankar P
2010-06-18 13:00 ` Catalin Marinas
2010-06-18 13:25 ` Sankar P
2010-06-22 6:54 ` Sankar P
2010-06-22 6:58 ` [PATCH] mm: kmemleak: Change kmemleak default buffer size Sankar P
2010-06-22 8:11 ` Pekka Enberg
2010-06-22 8:46 ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak Sankar P
2010-06-22 11:31 ` Paul Mundt
2010-06-22 12:05 ` Catalin Marinas
2010-06-22 12:14 ` Paul Mundt
2010-06-22 12:21 ` Pekka Enberg
2010-06-22 12:35 ` Catalin Marinas
2010-06-22 12:41 ` Pekka Enberg
2010-06-22 16:55 ` [PATCH] mm: kmemleak: Change kmemleak default buffer size Luis R. Rodriguez
2010-06-24 7:31 ` Sankar P
2010-06-24 18:56 ` Luis R. Rodriguez
[not found] ` <AANLkTim4mjw0BFshK_4RS6oDLLQMH_BF7BklU7EhETSj@mail.gmail.com>
2010-06-24 19:12 ` Luis R. Rodriguez
2010-06-24 19:17 ` Sankar P
2010-06-24 19:20 ` Luis R. Rodriguez
2010-06-24 19:27 ` Sankar P
2010-06-25 9:10 ` Luis R. Rodriguez
2010-06-25 9:18 ` Tejun Heo
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=20100617173604.GB28055@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=rnagarajan@novell.com \
--cc=sankar.curiosity@gmail.com \
--cc=teheo@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).