[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191105115431.GD26580@mbp>
Date: Tue, 5 Nov 2019 11:54:31 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Amir Goldstein <amir73il@...il.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: Re: 5.4-rc1 boot regression with kmemleak enabled
(sorry if you got this message twice; our SMTP server went bust)
On Tue, Nov 05, 2019 at 09:14:06AM +0200, Amir Goldstein 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'
This was fixed in 5.4-rc4, see commit 2abd839aa7e6 ("kmemleak: Do not
corrupt the object_list during clean-up").
--
Catalin
Powered by blists - more mailing lists