From: Nicolas Boichat <drinkcat@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Kees Cook <keescook@chromium.org>, Petr Mladek <pmladek@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Joe Lawrence <joe.lawrence@redhat.com>,
Sri Krishna chowdary <schowdary@nvidia.com>,
Uladzislau Rezki <urezki@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Changbin Du <changbin.du@intel.com>,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Catalin Marinas <catalin.marinas@arm.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: [PATCH] kmemleak: Increase maximum early log entries to 1000000
Date: Tue, 23 Jul 2019 15:26:05 +0800 [thread overview]
Message-ID: <20190723072605.103456-1-drinkcat@chromium.org> (raw)
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@chromium.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
next reply other threads:[~2019-07-23 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 7:26 Nicolas Boichat [this message]
2019-07-23 7:46 ` [PATCH] kmemleak: Increase maximum early log entries to 1000000 Dmitry Vyukov
2019-07-23 8:13 ` Nicolas Boichat
2019-07-23 8:21 ` Dmitry Vyukov
2019-07-23 22:17 ` Doug Anderson
2019-07-24 7:10 ` Dmitry Vyukov
2019-07-24 9:00 ` Andrey Ryabinin
2019-07-30 15:22 ` Nicolas Boichat
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=20190723072605.103456-1-drinkcat@chromium.org \
--to=drinkcat@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=changbin.du@intel.com \
--cc=dvyukov@google.com \
--cc=joe.lawrence@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=pmladek@suse.com \
--cc=schowdary@nvidia.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=yamada.masahiro@socionext.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).