[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190723072605.103456-1-drinkcat@chromium.org>
Date: Tue, 23 Jul 2019 15:26:05 +0800
From: Nicolas Boichat <drinkcat@...omium.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Kees Cook <keescook@...omium.org>,
Petr Mladek <pmladek@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
Joe Lawrence <joe.lawrence@...hat.com>,
Sri Krishna chowdary <schowdary@...dia.com>,
Uladzislau Rezki <urezki@...il.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Changbin Du <changbin.du@...el.com>,
linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Catalin Marinas <catalin.marinas@....com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>
Subject: [PATCH] kmemleak: Increase maximum early log entries to 1000000
When KASan is enabled, a lot of memory is allocated early on,
and kmemleak complains (this is on a 4GB RAM system):
kmemleak: Early log buffer exceeded (129846), please increase
DEBUG_KMEMLEAK_EARLY_LOG_SIZE
Let's increase the upper limit to 1M entry. That would take up
160MB of RAM at init (each early_log entry is 160 bytes), but
the memory would later be freed (early_log is __initdata).
Signed-off-by: Nicolas Boichat <drinkcat@...omium.org>
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index f567875b87657de..1a197b8125768b9 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -595,7 +595,7 @@ config DEBUG_KMEMLEAK
config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
int "Maximum kmemleak early log entries"
depends on DEBUG_KMEMLEAK
- range 200 40000
+ range 200 1000000
default 400
help
Kmemleak must track all the memory allocations to avoid
--
2.22.0.657.g960e92d24f-goog
Powered by blists - more mailing lists