syzbot


WARNING in try_charge

Status: fixed on 2018/09/26 21:51
Subsystems: cgroups mm xfs
[Documentation on labels]
Reported-by: syzbot+bab151e82a4e973fa325@syzkaller.appspotmail.com
Fix commit: 3100dab2aa09 mm: memcontrol: print proper OOM header when no eligible victim left
First crash: 2096d, last: 2034d
Discussions (3)
Title Replies (including bot) Last reply
[PATCH] mm, oom: OOM victims do not need to select next OOM victim unless __GFP_NOFAIL. 11 (11) 2018/08/28 21:17
[PATCH] memcg, oom: be careful about races when warning about no reclaimable task 18 (18) 2018/08/21 17:20
WARNING in try_charge 46 (53) 2018/08/09 21:05

Sample crash report:
Killed process 6527 (syz-executor2) total-vm:37704kB, anon-rss:2140kB, file-rss:0kB, shmem-rss:0kB
oom_reaper: reaped process 6527 (syz-executor2), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
------------[ cut here ]------------
oom_reaper: reaped process 6532 (syz-executor3), now anon-rss:0kB, file-rss:4kB, shmem-rss:0kB
Memory cgroup charge failed because of no reclaimable memory! This looks like a misconfiguration or a kernel bug.
WARNING: CPU: 1 PID: 6536 at mm/memcontrol.c:1705 mem_cgroup_oom mm/memcontrol.c:1704 [inline]
WARNING: CPU: 1 PID: 6536 at mm/memcontrol.c:1705 try_charge+0x734/0x1680 mm/memcontrol.c:2262
oom_reaper: reaped process 6518 (syz-executor0), now anon-rss:0kB, file-rss:4kB, shmem-rss:0kB
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 6536 Comm: syz-executor2 Not tainted 4.18.0-rc7-next-20180803+ #31
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1c9/0x2b4 lib/dump_stack.c:113
 panic+0x238/0x4e7 kernel/panic.c:184
 __warn.cold.8+0x163/0x1ba kernel/panic.c:536
 report_bug+0x252/0x2d0 lib/bug.c:186
 fixup_bug arch/x86/kernel/traps.c:178 [inline]
 do_error_trap+0x1fc/0x4d0 arch/x86/kernel/traps.c:296
 do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:316
 invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:996
RIP: 0010:mem_cgroup_oom mm/memcontrol.c:1704 [inline]
RIP: 0010:try_charge+0x734/0x1680 mm/memcontrol.c:2262
Code: 85 b8 04 00 00 8b b5 c8 fd ff ff 44 89 f2 4c 89 ff e8 f0 51 ff ff 84 c0 0f 85 31 08 00 00 48 c7 c7 60 17 13 87 e8 7c fe 85 ff <0f> 0b 48 8d 95 f8 fd ff ff 48 8b b5 c0 fd ff ff 48 b8 00 00 00 00
RSP: 0018:ffff8801a8637620 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff8801cbb5c980 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff816366f1 RDI: ffff8801a8637310
RBP: ffff8801a86378b0 R08: ffff8801b23001c0 R09: fffffbfff0ff11fc
R10: fffffbfff0ff11fc R11: ffffffff87f88fe3 R12: dffffc0000000000
R13: ffff8801a8637888 R14: 0000000000000000 R15: ffff8801cbb5c980
 memcg_kmem_charge_memcg+0x7c/0x120 mm/memcontrol.c:2592
 memcg_charge_slab mm/slab.h:283 [inline]
 kmem_getpages mm/slab.c:1415 [inline]
 cache_grow_begin+0x207/0x710 mm/slab.c:2677
 fallback_alloc+0x203/0x2c0 mm/slab.c:3219
 ____cache_alloc_node+0x1c7/0x1e0 mm/slab.c:3287
 __do_cache_alloc mm/slab.c:3356 [inline]
 slab_alloc mm/slab.c:3384 [inline]
 kmem_cache_alloc+0x1e5/0x760 mm/slab.c:3552
 shmem_alloc_inode+0x1b/0x40 mm/shmem.c:3515
 alloc_inode+0x63/0x190 fs/inode.c:210
 new_inode_pseudo+0x71/0x1a0 fs/inode.c:903
 new_inode+0x1c/0x40 fs/inode.c:932
 shmem_get_inode+0xf1/0x910 mm/shmem.c:2142
 __shmem_file_setup.part.48+0x83/0x2a0 mm/shmem.c:3871
 __shmem_file_setup mm/shmem.c:3865 [inline]
 shmem_file_setup+0x65/0x90 mm/shmem.c:3912
 __do_sys_memfd_create mm/memfd.c:304 [inline]
 __se_sys_memfd_create mm/memfd.c:247 [inline]
 __x64_sys_memfd_create+0x2af/0x4f0 mm/memfd.c:247
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x456b29
Code: Bad RIP value.
RSP: 002b:00007f91f0f04a88 EFLAGS: 00000246 ORIG_RAX: 000000000000013f
RAX: ffffffffffffffda RBX: 0000000020000740 RCX: 0000000000456b29
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000004c1c8d
RBP: 00000000009300a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000740 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004d5bb8 R14: 00000000004c9491 R15: 0000000000000000
Dumping ftrace buffer:
   (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (649):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/08/05 08:13 linux-next 116b181bb646 3476a2df .config console log report syz ci-upstream-linux-next-kasan-gce-root
2018/08/31 12:37 upstream 217c3e019675 a4718693 .config console log report ci-upstream-kasan-gce
2018/09/19 21:52 bpf 4c3d795cb012 7f125108 .config console log report ci-upstream-bpf-kasan-gce
2018/09/13 01:53 net-old cc4dfb7f70a3 71907daf .config console log report ci-upstream-net-this-kasan-gce
2018/09/26 19:14 bpf-next d0e13a1488ad 455b6354 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 17:51 bpf-next d0e13a1488ad 455b6354 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 16:12 bpf-next d0e13a1488ad 455b6354 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 12:36 bpf-next d0e13a1488ad 455b6354 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 10:44 bpf-next d0e13a1488ad 455b6354 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 08:59 bpf-next d0e13a1488ad 455b6354 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 05:26 bpf-next d0e13a1488ad b7e11289 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 02:39 bpf-next d0e13a1488ad b7e11289 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 01:18 bpf-next d0e13a1488ad b7e11289 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/26 00:03 bpf-next d0e13a1488ad b7e11289 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 21:12 bpf-next d0e13a1488ad b7e11289 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 19:37 bpf-next d0e13a1488ad b7e11289 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 15:51 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 14:34 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 13:58 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 12:43 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 11:21 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 10:01 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 08:56 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 07:50 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 05:30 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 04:08 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/25 02:24 bpf-next 788758d1fe87 0e7547d7 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 22:08 bpf-next 788758d1fe87 2f485cdf .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 17:29 bpf-next 788758d1fe87 2f485cdf .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 15:56 bpf-next 788758d1fe87 2f485cdf .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 14:44 bpf-next 788758d1fe87 2f485cdf .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 12:06 bpf-next 788758d1fe87 2f485cdf .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 05:37 bpf-next 788758d1fe87 28d9ac76 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 04:07 bpf-next 788758d1fe87 28d9ac76 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 02:38 bpf-next 788758d1fe87 28d9ac76 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/24 00:49 bpf-next 788758d1fe87 28d9ac76 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/23 23:43 bpf-next 788758d1fe87 28d9ac76 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/23 21:40 bpf-next 788758d1fe87 28d9ac76 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/23 19:39 bpf-next 788758d1fe87 28d9ac76 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/23 17:22 bpf-next 788758d1fe87 37079712 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/23 15:59 bpf-next 788758d1fe87 37079712 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/23 14:33 bpf-next 788758d1fe87 37079712 .config console log report ci-upstream-bpf-next-kasan-gce
2018/09/13 21:37 net-next-old a20625e49dde 19e9088b .config console log report ci-upstream-net-kasan-gce
2018/08/06 10:56 linux-next 116b181bb646 1beb8136 .config console log report ci-upstream-linux-next-kasan-gce-root
2018/07/27 06:31 linux-next d1e0b8e0cb7a 375a3e31 .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.