[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOQ4uxgy6THDG2NsNSQ+=FP+iSZKeCkNEM9PbxQSB5p5nHvoCA@mail.gmail.com>
Date: Tue, 5 Nov 2019 09:14:06 +0200
From: Amir Goldstein <amir73il@...il.com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Theodore Tso <tytso@....edu>, fstests <fstests@...r.kernel.org>,
Matthew Wilcox <willy@...radead.org>,
Michal Hocko <mhocko@...nel.org>, Qian Cai <cai@....pw>,
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: 5.4-rc1 boot regression with kmemleak enabled
Hi Catalin,
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.
I also tried moving kmemleak_init() back to its old location, since this
changes seemed unrelated to the commit. Didn't help either.
Let me know if you have any suggestion how to debug this.
Thanks,
Amir.
[1] https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-xfstests.md
Download attachment "defconfig" of type "application/octet-stream" (7580 bytes)
Powered by blists - more mailing lists