syzbot


WARNING in __vm_enough_memory

Status: upstream: reported C repro on 2019/04/23 10:25
Reported-by: syzbot+266a0c54afa72fa2f9ca@syzkaller.appspotmail.com
First crash: 2039d, last: 992d
Fix bisection the fix commit could be any of (bisect log):
  c6db52a88798 Linux 4.14.183
  4139fb08c05f Linux 4.14.187
  
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 WARNING in __vm_enough_memory tmpfs C error 35 630d 2039d 0/1 upstream: reported C repro on 2019/04/23 10:26
upstream WARNING in __vm_enough_memory lsm C 64 2039d 2501d 0/28 closed as invalid on 2019/07/30 01:01
android-414 WARNING in __vm_enough_memory C 10 1933d 2050d 0/1 public: reported C repro on 2019/04/12 00:01
android-49 WARNING in __vm_enough_memory C 72 1852d 2050d 0/3 public: reported C repro on 2019/04/12 00:00
upstream WARNING in __vm_enough_memory (2) kernel syz done 6 1678d 1681d 15/28 fixed on 2020/06/18 13:57
Last patch testing requests (8)
Created Duration User Patch Repo Result
2023/02/15 23:32 14m retest repro linux-4.14.y report log
2023/02/15 22:32 11m retest repro linux-4.14.y report log
2023/02/15 21:32 9m retest repro linux-4.14.y report log
2023/02/15 20:32 9m retest repro linux-4.14.y report log
2022/10/14 01:30 14m retest repro linux-4.14.y report log
2022/10/13 13:30 12m retest repro linux-4.14.y report log
2022/10/13 03:30 15m retest repro linux-4.14.y report log
2022/10/13 02:30 0m retest repro linux-4.14.y error
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2020/07/07 15:46 35m bisect fix linux-4.14.y OK (2) job log
2020/05/16 06:31 26m bisect fix linux-4.14.y OK (0) job log log
2020/04/16 06:08 22m bisect fix linux-4.14.y OK (0) job log log
2020/03/17 05:44 23m bisect fix linux-4.14.y OK (0) job log log
2020/02/16 05:20 24m bisect fix linux-4.14.y OK (0) job log log
2020/01/11 19:20 23m bisect fix linux-4.14.y OK (0) job log log
2019/11/29 04:10 24m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
IPVS: ftp: loaded support on port[0] = 21
memory commitment underflow
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4634 at mm/util.c:622 __vm_enough_memory.cold+0x18/0x59 mm/util.c:622
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 4634 Comm: systemd-udevd Not tainted 4.14.246-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 panic+0x1f9/0x42d kernel/panic.c:183
 __warn.cold+0x20/0x44 kernel/panic.c:547
 report_bug+0x208/0x250 lib/bug.c:183
 fixup_bug arch/x86/kernel/traps.c:177 [inline]
 fixup_bug arch/x86/kernel/traps.c:172 [inline]
 do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
 invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:__vm_enough_memory.cold+0x18/0x59 mm/util.c:622
RSP: 0018:ffff88809a5d7bf8 EFLAGS: 00010286
RAX: 000000000000001b RBX: 000000000000000a RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff88809a5cec98 RDI: ffffed10134baf75
RBP: 0000000000000001 R08: 000000000000001b R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88809a745900
R13: ffffffff88feb1e0 R14: fff8000000005b68 R15: 0000000000000d36
 dup_mmap kernel/fork.c:643 [inline]
 dup_mm kernel/fork.c:1199 [inline]
 copy_mm kernel/fork.c:1254 [inline]
 copy_process.part.0+0x4ab3/0x71c0 kernel/fork.c:1790
 copy_process kernel/fork.c:1605 [inline]
 _do_fork+0x184/0xc80 kernel/fork.c:2091
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f7bee95038b
RSP: 002b:00007fffe98e9c10 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007fffe98e9c10 RCX: 00007f7bee95038b
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 00007fffe98e9c60 R08: 00007f7befb018c0 R09: 0000000000000210
R10: 00007f7befb01b90 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000020 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (14):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/09/13 08:31 linux-4.14.y f96eb53cbd76 3ce60af8 .config console log report syz C ci2-linux-4-14 WARNING in __vm_enough_memory
2020/06/07 15:46 linux-4.14.y c6db52a88798 2c2b926c .config console log report syz C ci2-linux-4-14
2019/04/25 08:38 linux-4.14.y 68d7a45eec10 8e3c52b1 .config console log report syz C ci2-linux-4-14
2019/04/23 09:56 linux-4.14.y 68d7a45eec10 53199d6e .config console log report syz C ci2-linux-4-14
2022/03/05 15:26 linux-4.14.y e853993d29aa 45a13a73 .config console log report info ci2-linux-4-14 WARNING in __vm_enough_memory
2021/05/06 00:51 linux-4.14.y 7d7d1c0ab3eb 06c27ff5 .config console log report info ci2-linux-4-14 WARNING in __vm_enough_memory
2021/04/09 15:01 linux-4.14.y 0cc244011f40 6a81331a .config console log report info ci2-linux-4-14 WARNING in __vm_enough_memory
2021/03/25 05:10 linux-4.14.y 670d6552eda8 607e3baf .config console log report info ci2-linux-4-14 WARNING in __vm_enough_memory
2021/03/14 00:34 linux-4.14.y c7150cd2fa8c 4a003785 .config console log report info ci2-linux-4-14 WARNING in __vm_enough_memory
2021/01/26 21:27 linux-4.14.y 2d2791fce891 55a7d4df .config console log report info ci2-linux-4-14 WARNING in __vm_enough_memory
2021/01/11 23:27 linux-4.14.y ec822b3e8bf4 2c1f2513 .config console log report info ci2-linux-4-14
2020/01/17 05:20 linux-4.14.y c04fc6fa5c96 3de7aabb .config console log report ci2-linux-4-14
2019/12/12 13:55 linux-4.14.y a844dc4c5442 d973f528 .config console log report ci2-linux-4-14
2019/04/23 09:24 linux-4.14.y 68d7a45eec10 53199d6e .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.