Messages in this thread | | | Date | Mon, 14 Oct 2019 09:45:01 -0400 | From | "Theodore Y. Ts'o" <> | Subject | Re: [REGRESSION] kmemleak: commit c566586818 causes failure to boot |
| |
On Mon, Oct 14, 2019 at 01:51:15PM +0100, Catalin Marinas wrote: > In your case, CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF=y, so it disables itself > irrespective of the pool size and trips over the bug. Even with default > off, it still involves the clean-up since kmemleak needs to track early > allocations in case it is turned on by the kmemleak=on cmdline option. > > So I think 16000 is sufficient in your case, the default-off triggered > the bug (well, unless you find in the logs "kmemleak: Memory pool empty, > consider increasing CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE").
Ah, got it, thanks for the clarification!
- Ted
| |