linux-kernel - Re: 5.4-rc1 boot regression with kmemleak enabled

lists.openwall.net		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 linux-cve-announce 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]

Message-Id: <036DEC84-92EE-4A47-B078-ADC605482255@lca.pw>
Date:   Tue, 5 Nov 2019 04:23:39 -0500
From:   Qian Cai <cai@....pw>
To:     Amir Goldstein <amir73il@...il.com>
Cc:     Catalin Marinas <catalin.marinas@....com>,
        Theodore Tso <tytso@....edu>,
        fstests <fstests@...r.kernel.org>,
        Matthew Wilcox <willy@...radead.org>,
        Michal Hocko <mhocko@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux MM <linux-mm@...ck.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: 5.4-rc1 boot regression with kmemleak enabled



> On Nov 5, 2019, at 2:14 AM, Amir Goldstein <amir73il@...il.com> wrote:
> 
> My kvm-xfstests [1] VM doesn't boot with kmemleak enabled since commit
> c5665868183f ("mm: kmemleak: use the memory pool for early allocations").
> 
> There is no console output when running:
> 
> $ kvm -boot order=c -net none -machine type=pc,accel=kvm:tcg -cpu host \
>    -drive file=$ROOTFS,if=virtio,snapshot=on -vga none -nographic \
>    -smp 2 -m 2048 -serial mon:stdio --kernel $KERNEL \
>    --append 'root=/dev/vda console=ttyS0,115200'
> 
> $ kvm --version
> QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.19)
> Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
> 
> Attached defconfig saved by 'make savedefconfig'.
> 
> I tried increasing DEBUG_KMEMLEAK_MEM_POOL_SIZE, which did not help.

It probably use a bit more memory than before. Does lower the parameter help? Eventually, It should boot with POOL_SIZE=0, no?