[<prev] [next>] [day] [month] [year] [list]
Message-ID: <576c7510.SAiRMzo9wNiGCq5R%fengguang.wu@intel.com>
Date: Fri, 24 Jun 2016 07:47:28 +0800
From: kernel test robot <fengguang.wu@...el.com>
To: Mel Gorman <mgorman@...e.de>
Cc: LKP <lkp@...org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Linux Memory Management List <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>, wfg@...ux.intel.com
Subject: [mm] c3e3459c92: WARNING: CPU: 1 PID: 249 at mm/util.c:519
__vm_enough_memory
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit c3e3459c92a22be17145cdd9d86a8acc74afa5cf
Author: Mel Gorman <mgorman@...hsingularity.net>
AuthorDate: Thu Jun 23 09:59:20 2016 +1000
Commit: Stephen Rothwell <sfr@...b.auug.org.au>
CommitDate: Thu Jun 23 09:59:20 2016 +1000
mm: move vmscan writes and file write accounting to the node
As reclaim is now node-based, it follows that page write activity due to
page reclaim should also be accounted for on the node. For consistency,
also account page writes and page dirtying on a per-node basis.
After this patch, there are a few remaining zone counters that may appear
strange but are fine. NUMA stats are still per-zone as this is a
user-space interface that tools consume. NR_MLOCK, NR_SLAB_*,
NR_PAGETABLE, NR_KERNEL_STACK and NR_BOUNCE are all allocations that
potentially pin low memory and cannot trivially be reclaimed on demand.
This information is still useful for debugging a page allocation failure
warning.
Link: http://lkml.kernel.org/r/1466518566-30034-20-git-send-email-mgorman@techsingularity.net
Signed-off-by: Mel Gorman <mgorman@...hsingularity.net>
Acked-by: Vlastimil Babka <vbabka@...e.cz>
Cc: Johannes Weiner <hannes@...xchg.org>
Cc: Rik van Riel <riel@...riel.com>
Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
+------------------------------------------------+------------+------------+---------------+
| | e426f7b4ad | c3e3459c92 | next-20160623 |
+------------------------------------------------+------------+------------+---------------+
| boot_successes | 93 | 0 | 0 |
| boot_failures | 12 | 16 | 29 |
| IP-Config:Auto-configuration_of_network_failed | 12 | 12 | 16 |
| WARNING:at_mm/util.c:#__vm_enough_memory | 0 | 14 | 27 |
| backtrace:vm_mmap_pgoff | 0 | 13 | 21 |
| backtrace:SyS_mmap_pgoff | 0 | 13 | 21 |
| backtrace:SyS_mmap | 0 | 13 | 21 |
| BUG:kernel_test_hang | 0 | 2 | |
| backtrace:do_execveat_common | 0 | 1 | |
| backtrace:SyS_execve | 0 | 1 | |
| backtrace:_do_fork | 0 | 0 | 6 |
| backtrace:SyS_clone | 0 | 0 | 6 |
+------------------------------------------------+------------+------------+---------------+
[ 7.529499] systemd-sysv-generator[249]: Ignoring K01watchdog symlink in rc6.d, not generating watchdog.service.
[ 7.530773] systemd-fstab-generator[247]: Parsing /etc/fstab
[ 7.535727] ------------[ cut here ]------------
[ 7.535734] WARNING: CPU: 1 PID: 249 at mm/util.c:519 __vm_enough_memory+0x6f/0x1d0
[ 7.535738] memory commitment underflow
[ 7.535738] CPU: 1 PID: 249 Comm: systemd-sysv-ge Not tainted 4.7.0-rc4-00215-gc3e3459 #1
[ 7.535739] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
[ 7.535742] 0000000000000000 ffff88003f1f3cb8 ffffffff8143c528 ffff88003f1f3d08
[ 7.535745] 0000000000000000 ffff88003f1f3cf8 ffffffff810a9976 000002073f1f3de0
[ 7.535747] 0000000000000001 ffffffffff0a01aa 0000000000000001 ffff88003f4d52c0
[ 7.535747] Call Trace:
[ 7.535751] [<ffffffff8143c528>] dump_stack+0x65/0x8d
[ 7.535754] [<ffffffff810a9976>] __warn+0xb6/0xe0
[ 7.535756] [<ffffffff810a99ea>] warn_slowpath_fmt+0x4a/0x50
[ 7.535757] [<ffffffff8115e84f>] __vm_enough_memory+0x6f/0x1d0
[ 7.535761] [<ffffffff813d7a8e>] security_vm_enough_memory_mm+0x4e/0x60
[ 7.535765] [<ffffffff81176fc1>] mmap_region+0x131/0x590
[ 7.535767] [<ffffffff811777dd>] do_mmap+0x3bd/0x4a0
[ 7.535768] [<ffffffff8115e4d5>] vm_mmap_pgoff+0x85/0xd0
[ 7.535770] [<ffffffff811754d1>] SyS_mmap_pgoff+0xb1/0xc0
[ 7.535773] [<ffffffff81023376>] SyS_mmap+0x16/0x20
[ 7.535777] [<ffffffff81c25df6>] entry_SYSCALL_64_fastpath+0x1e/0xa8
git bisect start 5c4d1ca9cfa71d9515ce5946cfc6497d22b1108e 33688abb2802ff3a230bd2441f765477b94cc89e --
git bisect good 8a5968b8e3f00a767f43f88805f3d288756570e0 # 05:57 22+ 6 Merge remote-tracking branch 'wireless-drivers-next/master'
git bisect good fdb4089f350a5e41bf8cf99838be4142e7fffda9 # 05:59 22+ 6 Merge remote-tracking branch 'spi/for-next'
git bisect good d262aacb56c190b7b1cfeb0b9edca24e38147ade # 06:00 22+ 4 Merge remote-tracking branch 'char-misc/char-misc-next'
git bisect good b36d4f39637feedd4de59b79f9efbe57419a6090 # 06:03 22+ 6 Merge remote-tracking branch 'pwm/for-next'
git bisect good 97730d0a214f1be8043cc2e06c7510d8a93d559b # 06:05 22+ 6 Merge remote-tracking branch 'livepatching/for-next'
git bisect good 82b3e0323b0abaa917a383a61e48b3028a14311a # 06:07 22+ 6 Merge remote-tracking branch 'rtc/rtc-next'
git bisect bad 204502b144a6e67a067aa476e4c0149815e1be8e # 06:07 0- 5 Merge branch 'akpm-current/current'
git bisect good 7f8d9cfe93d5d5fcbd3719e96782922f55c17947 # 06:32 22+ 2 thp: handle file pages in split_huge_pmd()
git bisect bad ead73aa015eae132a31e8b1324931781d5cd1ba9 # 06:49 0- 15 mm: update the comment in __isolate_free_page
git bisect good 44918a56e3af3c802cd0daeb9eba5ecc22fa4a96 # 07:04 22+ 2 mm-vmscan-move-lru-lists-to-node-fix
git bisect bad e128e3836e98482661449dc811d10741ba75be61 # 07:10 1- 23 mm, vmscan: only wakeup kswapd once per node for the requested classzone
git bisect good b4f255ed4b93bb514f0e79cdbb2c6c2620e40325 # 07:16 22+ 0 mm, vmscan: make shrink_node decisions more node-centric
git bisect good 6123aec614297a16b0446d3f4046020a7d692857 # 07:19 22+ 4 mm: move page mapped accounting to the node
git bisect good e426f7b4ade5e59ee0b504d2472d850ded146196 # 07:21 22+ 12 mm: move most file-based accounting to the node
git bisect bad 60747f09fcc202a80bba0e8a97ae0835befd34d2 # 07:21 0- 29 mm, vmscan: update classzone_idx if buffer_heads_over_limit
git bisect bad c3e3459c92a22be17145cdd9d86a8acc74afa5cf # 07:21 0- 16 mm: move vmscan writes and file write accounting to the node
# first bad commit: [c3e3459c92a22be17145cdd9d86a8acc74afa5cf] mm: move vmscan writes and file write accounting to the node
git bisect good e426f7b4ade5e59ee0b504d2472d850ded146196 # 07:24 69+ 12 mm: move most file-based accounting to the node
# extra tests with CONFIG_DEBUG_INFO_REDUCED
git bisect bad c3e3459c92a22be17145cdd9d86a8acc74afa5cf # 07:24 0- 4 mm: move vmscan writes and file write accounting to the node
# extra tests on HEAD of linux-next/master
git bisect bad 5c4d1ca9cfa71d9515ce5946cfc6497d22b1108e # 07:25 0- 29 Add linux-next specific files for 20160623
# extra tests on tree/branch linux-next/master
git bisect bad 5c4d1ca9cfa71d9515ce5946cfc6497d22b1108e # 07:25 0- 29 Add linux-next specific files for 20160623
# extra tests with first bad commit reverted
git bisect good eb910f180124bc59e1c1d2bf3a6f036526d3bf16 # 07:27 69+ 12 Revert "mm: move vmscan writes and file write accounting to the node"
# extra tests on tree/branch linus/master
git bisect good da01e18a37a57f360222d3a123b8f6994aa1ad14 # 07:46 67+ 4 x86: avoid avoid passing around 'thread_info' in stack dumping code
# extra tests on tree/branch linux-next/master
git bisect bad 5c4d1ca9cfa71d9515ce5946cfc6497d22b1108e # 07:46 0- 29 Add linux-next specific files for 20160623
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/lkp Intel Corporation
Download attachment "dmesg-vm-kbuild-1G-6:20160624003936:x86_64-randconfig-s0-06231721:4.7.0-rc4-00215-gc3e3459:1.gz" of type "application/gzip" (18498 bytes)
Download attachment "dmesg-vm-kbuild-1G-1:20160624010922:x86_64-randconfig-s0-06231721:4.7.0-rc4-00214-ge426f7b:1.gz" of type "application/gzip" (18218 bytes)
View attachment "config-4.7.0-rc4-00215-gc3e3459" of type "text/plain" (98590 bytes)
Powered by blists - more mailing lists