Messages in this thread Patch in this message | | | From | Nicolas Boichat <> | Subject | [PATCH] kmemleak: Increase maximum early log entries to 1000000 | Date | Tue, 23 Jul 2019 15:26:05 +0800 |
| |
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
| |