fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Theodore Tso <tytso@mit.edu>, fstests <fstests@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	Michal Hocko <mhocko@kernel.org>,
	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 04:23:39 -0500	[thread overview]
Message-ID: <036DEC84-92EE-4A47-B078-ADC605482255@lca.pw> (raw)
In-Reply-To: <CAOQ4uxgy6THDG2NsNSQ+=FP+iSZKeCkNEM9PbxQSB5p5nHvoCA@mail.gmail.com>



> On Nov 5, 2019, at 2:14 AM, Amir Goldstein <amir73il@gmail.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?

  parent reply	other threads:[~2019-11-05  9:23 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 [this message]
2019-11-05 11:54 ` Catalin Marinas
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=036DEC84-92EE-4A47-B078-ADC605482255@lca.pw \
    --to=cai@lca.pw \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=catalin.marinas@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).