linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sankar P <sankar.curiosity@gmail.com>
To: penberg@cs.helsinki.fi
Cc: lethal@linux-sh.org, linux-sh@vger.kernel.org,
	linux-kernel@vger.kernel.org, lrodriguez@atheros.com,
	catalin.marinas@arm.com, rnagarajan@novell.com, teheo@novell.com,
	linux-mm@kvack.org, paulmck@linux.vnet.ibm.com, mingo@elte.hu,
	akpm@linux-foundation.org, Sankar P <sankar.curiosity@gmail.com>
Subject: [PATCH] kmemleak: config-options: Default buffer size for kmemleak
Date: Tue, 22 Jun 2010 14:16:43 +0530	[thread overview]
Message-ID: <1277196403-20836-1-git-send-email-sankar.curiosity@gmail.com> (raw)
In-Reply-To: <4C20702C.1080405@cs.helsinki.fi>

If we try to find the memory leaks in kernel that is
compiled with 'make defconfig', the default buffer size
of DEBUG_KMEMLEAK_EARLY_LOG_SIZE seem to be inadequate.

Change the buffer size from 400 to 1000,
which is sufficient for most cases.

Signed-off-by: Sankar P <sankar.curiosity@gmail.com>
---

Thanks to Pekka Enberg's comments on my previous mail, I am sending a better patch,
and adding new reviewers as suggested by the get_maintainer script. 

 lib/Kconfig.debug |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index e722e9d..5eb9463 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -382,7 +382,7 @@ config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
 	int "Maximum kmemleak early log entries"
 	depends on DEBUG_KMEMLEAK
 	range 200 40000
-	default 400
+	default 1000
 	help
 	  Kmemleak must track all the memory allocations to avoid
 	  reporting false positives. Since memory may be allocated or
-- 
1.6.4.2

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-22  8:47 UTC|newest]

Thread overview: 18+ 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
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         ` Sankar P [this message]
2010-06-22 11:31           ` [PATCH] kmemleak: config-options: Default buffer size for kmemleak 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

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=1277196403-20836-1-git-send-email-sankar.curiosity@gmail.com \
    --to=sankar.curiosity@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=rnagarajan@novell.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).