Messages in this thread | | | Subject | Re: [PATCH] kmemleak: Increase maximum early log entries to 1000000 | From | Andrey Ryabinin <> | Date | Wed, 24 Jul 2019 12:00:53 +0300 |
| |
On 7/23/19 11:13 AM, Nicolas Boichat wrote: > On Tue, Jul 23, 2019 at 3:46 PM Dmitry Vyukov <dvyukov@google.com> wrote: >> >> On Tue, Jul 23, 2019 at 9:26 AM Nicolas Boichat <drinkcat@chromium.org> wrote: >>> >>> 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). >> >> Interesting. Is it on an arm64 system? > > Yes arm64. And this is chromiumos-4.19 tree. I didn't try to track > down where these allocations come from... >
Is this still a problem in upstream tree? 4.19 doesn't have fed84c785270 ("mm/memblock.c: skip kmemleak for kasan_init()")
| |