On Tue, Aug 13, 2019 at 08:35:54AM -0400, Qian Cai wrote: > On Mon, 2019-08-12 at 17:06 +0100, Catalin Marinas wrote: > > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > > index 4d39540011e2..39df06ffd9f4 100644 > > --- a/lib/Kconfig.debug > > +++ b/lib/Kconfig.debug > > @@ -592,17 +592,18 @@ config DEBUG_KMEMLEAK > > In order to access the kmemleak file, debugfs needs to be > > mounted (usually at /sys/kernel/debug). > > > > -config DEBUG_KMEMLEAK_EARLY_LOG_SIZE > > - int "Maximum kmemleak early log entries" > > +config DEBUG_KMEMLEAK_MEM_POOL_SIZE > > + int "Kmemleak memory pool size" > > depends on DEBUG_KMEMLEAK > > range 200 40000 > > default 16000 > > Hmm, this seems way too small. My previous round of testing with > kmemleak.mempool=524288 works quite well on all architectures.
We can change the upper bound here to 1M but I'd keep the default sane. Not everyone is running tests under OOM. -- Catalin
