kernel BUG at mm/vmstat.c:LINE!

12 views
Skip to first unread message

syzbot

unread,
Apr 16, 2019, 10:25:07 PM4/16/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 12ae58ca Linux 4.4.178
git tree: linux-4.4.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1077d4a0a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=5ef6f190eb5ce732
dashboard link: https://syzkaller.appspot.com/bug?extid=88b218e7d542b84fb4db
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

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

------------[ cut here ]------------
kernel BUG at mm/vmstat.c:1425!
invalid opcode: 0000 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 16 Comm: kworker/1:0 Not tainted 4.4.178 #2
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: vmstat vmstat_update
task: ffff88012b7a4440 ti: ffff88012b7a8000 task.ti: ffff88012b7a8000
RIP: 0010:[<ffffffff8129effc>] [<ffffffff8129effc>] vmstat_update
mm/vmstat.c:1425 [inline]
RIP: 0010:[<ffffffff8129effc>] [<ffffffff8129effc>]
vmstat_update+0x8c/0xc0 mm/vmstat.c:1396
RSP: 0018:ffff88012b7abd70 EFLAGS: 00010293
RAX: 0000000000000001 RBX: ffff88012b70b880 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff82f4ccc7 RDI: ffffffff82f0761a
RBP: ffff88012b7abd90 R08: 0000000000000000 R09: 0000000000000003
R10: 0000000000000001 R11: 0000000000000000 R12: ffff88012c116880
R13: ffffe8ffffd0a400 R14: ffff88012c110de0 R15: ffffffff834354f8
FS: 0000000000000000(0000) GS:ffff88012c100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6f7d559150 CR3: 00000000b848c000 CR4: 00000000001406f0
Stack:
ffff88012b70b880 ffff88012c116880 ffffe8ffffd0a400 ffff88012c110de0
ffff88012b7abe00 ffffffff8119354d ffffffff811934b4 ffff88012c1168e0
0000000000000000 ffffffff84311ed0 ffffffff83da6790 0000000000000000
Call Trace:
[<ffffffff8119354d>] process_one_work+0x23d/0x800 kernel/workqueue.c:2064
[<ffffffff81193b59>] worker_thread+0x49/0x460 kernel/workqueue.c:2196
[<ffffffff81198da5>] kthread+0xe5/0x100 drivers/block/aoe/aoecmd.c:1311
[<ffffffff82668fd5>] ret_from_fork+0x55/0x80 arch/x86/entry/entry_64.S:510
Code: 41 5c 41 5d 41 5e 5d c3 e8 f2 b9 62 00 83 f8 3f 77 1b 89 c0 f0 48 0f
ab 05 ea 2e 07 03 72 0c 48 83 c4 08 41 5c 41 5d 41 5e 5d c3 <0f> 0b 80 3d
f1 70 16 02 00 75 dc be 75 00 00 00 48 c7 c7 8f eb
RIP [<ffffffff8129effc>] vmstat_update+0x8c/0xc0 mm/vmstat.c:1427
RSP <ffff88012b7abd70>
---[ end trace 74541c3732510038 ]---


---
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

unread,
Dec 2, 2019, 2:15:05 AM12/2/19
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages