[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1277196403-20836-1-git-send-email-sankar.curiosity@gmail.com>
Date: Tue, 22 Jun 2010 14:16:43 +0530
From: Sankar P <sankar.curiosity@...il.com>
To: penberg@...helsinki.fi
Cc: lethal@...ux-sh.org, linux-sh@...r.kernel.org,
linux-kernel@...r.kernel.org, lrodriguez@...eros.com,
catalin.marinas@....com, rnagarajan@...ell.com, teheo@...ell.com,
linux-mm@...ck.org, paulmck@...ux.vnet.ibm.com, mingo@...e.hu,
akpm@...ux-foundation.org, Sankar P <sankar.curiosity@...il.com>
Subject: [PATCH] kmemleak: config-options: Default buffer size for kmemleak
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@...il.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 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