kernel BUG at mm/vmstat.c:LINE!

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 62872f95 Merge 4.4.174 into android-4.4
git tree: android-4.4
console output: https://syzkaller.appspot.com/x/log.txt?x=14632bc7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=47bc4dd423780c4a
dashboard link: https://syzkaller.appspot.com/bug?extid=1b6600b2870ce68ffedc
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1700259d200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=104e415f200000

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+1b6600...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at mm/vmstat.c:1425!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 2417 Comm: kworker/0:2 Not tainted 4.4.174+ #4
Workqueue: vmstat vmstat_update
task: ffff8800b3358000 task.stack: ffff8801cf9b8000
RIP: 0010:[<ffffffff8140c9f9>] [<ffffffff8140c9f9>] vmstat_update
mm/vmstat.c:1425 [inline]
RIP: 0010:[<ffffffff8140c9f9>] [<ffffffff8140c9f9>]
vmstat_update+0x99/0xb0 mm/vmstat.c:1396
RSP: 0018:ffff8801cf9bfbc0 EFLAGS: 00010287
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff81b0abec RDI: ffff8800b33583f8
RBP: ffff8801cf9bfbe0 R08: ffffffff82836948 R09: ffff8800b3358910
R10: ffffffff83a189d0 R11: 0000000000000000 R12: ffff8801db61b380
R13: ffff8801cf9bfc78 R14: ffff8801d873da00 R15: ffff8801db61df00
FS: 0000000000000000(0000) GS:ffff8801db600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000002000020a CR3: 00000000b4402000 CR4: 00000000001606b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Stack:
0000000000000000 ffff8801db61b380 ffff8801cf9bfc78 ffff8801d873da00
ffff8801cf9bfd00 ffffffff81122c25 ffffffff81122b42 ffffffff81159431
ffff8801d873da48 ffff8801d9e8f400 ffff880100000000 ffff8801d873da20
Call Trace:
[<ffffffff81122c25>] process_one_work+0x825/0x1720 kernel/workqueue.c:2064
[<ffffffff81124004>] worker_thread+0x4e4/0xf50 kernel/workqueue.c:2196
[<ffffffff811342c3>] kthread+0x273/0x310 kernel/kthread.c:211
[<ffffffff82718fc5>] ret_from_fork+0x55/0x80 arch/x86/entry/entry_64.S:537
Code: 89 f6 e8 4b 95 d1 ff 5b 41 5c 41 5d 41 5e 5d c3 e8 cd e3 6f 00 89 c0
f0 48 0f ab 05 92 f4 c1 02 72 09 5b 41 5c 41 5d 41 5e 5d c3 <0f> 0b e8 c0
84 07 00 eb af 0f 1f 40 00 66 2e 0f 1f 84 00 00 00
RIP [<ffffffff8140c9f9>] vmstat_update+0x99/0xb0 mm/vmstat.c:1427
RSP <ffff8801cf9bfbc0>
---[ end trace a67f4ebd1db05737 ]---


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches