From: Qian Cai <cai@gmx.us>
To: linux-kernel@vger.kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>
Subject: kmemleak: Early log buffer exceeded (525980) during boot
Date: Thu, 08 Nov 2018 16:23:18 -0500 [thread overview]
Message-ID: <1541712198.12945.12.camel@gmx.us> (raw)
The maximum value for DEBUG_KMEMLEAK_EARLY_LOG_SIZE is only 40000, so it
disables kmemleak every time on this aarch64 server running the latest mainline
(b00d209).
# echo scan > /sys/kernel/debug/kmemleak
-bash: echo: write error: Device or resource busy
Any idea on how to enable kmemleak there?
next reply other threads:[~2018-11-08 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 21:23 Qian Cai [this message]
2018-11-10 15:08 ` Qian Cai
2018-11-10 16:59 ` Catalin Marinas
2018-11-10 17:42 ` Qian Cai
2018-11-14 2:31 ` Qian Cai
2018-11-28 4:21 ` Qian Cai
2018-12-05 14:38 ` Dmitry Vyukov
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=1541712198.12945.12.camel@gmx.us \
--to=cai@gmx.us \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®