From: kernel test robot <ying.huang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: lkp@01.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [lkp] [block] c1a6680dfd: OOM possibility increased from 50%-83%
Date: Tue, 10 Nov 2015 09:42:17 +0800 [thread overview]
Message-ID: <87mvumd406.fsf@yhuang-dev.intel.com> (raw)
FYI, we noticed the below changes on
git://git.infradead.org/users/hch/block.git nvme-loop.2
commit c1a6680dfd43af25bdfd5a22a7fe6efc16ba56f6 ("block: defer timeouts to a workqueue")
As below, just FYI. Although the memory size of virtual machine is too
small, your commit may increased memory usage.
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-intel12-openwrt-i386/boot/openwrt-i386.cgz/i386-randconfig-a0-201545/gcc-5/1
commit:
344c23116aa2003811927925a8462e57311e6467
c1a6680dfd43af25bdfd5a22a7fe6efc16ba56f6
344c23116aa20038 c1a6680dfd43af25bdfd5a22a7
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
:30 50% 15:30 kmsg.Kernel_Offset:disabled
1:30 -3% :30 kmsg.hrtimer:interrupt_took#ns
:30 50% 15:30 dmesg.Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes
:30 50% 15:30 dmesg.Mem-Info
:30 50% 15:30 dmesg.invoked_oom-killer:gfp_mask=0x
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-kbuild-yocto-i386/boot/yocto-minimal-i386.cgz/i386-randconfig-a0-201545/gcc-5/1
commit:
344c23116aa2003811927925a8462e57311e6467
c1a6680dfd43af25bdfd5a22a7fe6efc16ba56f6
344c23116aa20038 c1a6680dfd43af25bdfd5a22a7
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
:36 72% 26:36 kmsg.Kernel_Offset:disabled
:36 72% 26:36 dmesg.Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes
:36 72% 26:36 dmesg.Mem-Info
:36 72% 26:36 dmesg.invoked_oom-killer:gfp_mask=0x
=========================================================================================
tbox_group/testcase/rootfs/kconfig/compiler/sleep:
vm-vp-quantal-i386/boot/quantal-core-i386.cgz/i386-randconfig-a0-201545/gcc-5/1
commit:
344c23116aa2003811927925a8462e57311e6467
c1a6680dfd43af25bdfd5a22a7fe6efc16ba56f6
344c23116aa20038 c1a6680dfd43af25bdfd5a22a7
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
:12 83% 10:12 kmsg.Kernel_Offset:disabled
:12 83% 10:12 dmesg.Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes
:12 83% 10:12 dmesg.Mem-Info
:12 83% 10:12 dmesg.invoked_oom-killer:gfp_mask=0x
vm-intel12-openwrt-i386: qemu-system-i386 -enable-kvm
Memory: 192M
vm-kbuild-yocto-i386: qemu-system-i386 -enable-kvm
Memory: 320M
vm-vp-quantal-i386: qemu-system-i386 -enable-kvm -cpu Haswell,+smep,+smap
Memory: 360M
Thanks,
Ying Huang
reply other threads:[~2015-11-10 1:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87mvumd406.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=hch@lst.de \
--cc=lkp@01.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