From: Catalin Marinas <catalin.marinas@arm.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Theodore Tso <tytso@mit.edu>, fstests <fstests@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>, Qian Cai <cai@lca.pw>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 5.4-rc1 boot regression with kmemleak enabled
Date: Tue, 5 Nov 2019 11:54:31 +0000 [thread overview]
Message-ID: <20191105115431.GD26580@mbp> (raw)
In-Reply-To: <CAOQ4uxgy6THDG2NsNSQ+=FP+iSZKeCkNEM9PbxQSB5p5nHvoCA@mail.gmail.com>
(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
next prev parent reply other threads:[~2019-11-05 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 7:14 5.4-rc1 boot regression with kmemleak enabled Amir Goldstein
2019-11-05 9:02 ` Catalin Marinas
2019-11-05 9:23 ` Qian Cai
2019-11-05 11:54 ` Catalin Marinas [this message]
2019-11-05 12:33 ` Amir Goldstein
2019-11-05 15:30 ` Catalin Marinas
2019-11-05 18:17 ` Amir Goldstein
2019-11-05 18:22 ` Catalin Marinas
2019-11-05 18:49 ` Thomas Gleixner
2019-11-05 19:26 ` Amir Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191105115431.GD26580@mbp \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=cai@lca.pw \
--cc=fstests@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.