lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 20 Aug 2020 21:01:33 -0400
From:   Qian Cai <>
To:     kernel test robot <>
Cc:     Catalin Marinas <>,
        Linus Torvalds <>,
        Matthew Wilcox <>,
        Michal Hocko <>,
        Andrew Morton <>,
        LKML <>,
Subject: Re: [mm] c566586818:

On Tue, Aug 18, 2020 at 08:23:51AM +0800, kernel test robot wrote:
> Greeting,
> FYI, we noticed the following commit (built with gcc-9):
> commit: c5665868183fec689dbab9fb8505188b2c4f0757 ("mm: kmemleak: use the memory pool for early allocations")

I might see one of those early boot failure before. In my case, the bare-metal
system was reset. Can you try to narrow down to a smaller
CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE (assume 0 works if your bisecting was
correct) that works?

Powered by blists - more mailing lists