syzbot


BUG: unable to handle kernel paging request in mm_update_next_owner

Status: auto-closed as invalid on 2020/09/24 23:44
Reported-by: syzbot+6bcd6a8f82b51f41aed6@syzkaller.appspotmail.com
First crash: 1638d, last: 1638d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 BUG: unable to handle kernel paging request in mm_update_next_owner 21 1019d 1546d 0/1 auto-closed as invalid on 2022/06/06 03:00
upstream BUG: unable to handle kernel paging request in mm_update_next_owner kernel 11 1477d 1588d 0/28 auto-closed as invalid on 2021/03/04 20:21
linux-4.14 general protection fault in mm_update_next_owner (2) 6 1296d 1385d 0/1 auto-closed as invalid on 2021/09/01 20:39
upstream BUG: unable to handle kernel paging request in mm_update_next_owner (2) kernel 1 1113d 1109d 0/28 auto-closed as invalid on 2022/01/03 02:17

Sample crash report:
BUG: unable to handle kernel paging request at ffff87fffffffe98
IP: mm_update_next_owner+0x3e5/0x5b0 kernel/exit.c:452
PGD 0 P4D 0 
Oops: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 15730 Comm: syz-executor.3 Not tainted 4.14.182-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880708c4680 task.stack: ffff8881c16f8000
RIP: 0010:mm_update_next_owner+0x3e5/0x5b0 kernel/exit.c:452
RSP: 0018:ffff8881c16ffd48 EFLAGS: 00010246
RAX: 1ffff0ffffffffd3 RBX: dffffc0000000000 RCX: 1ffff1100e1189e5
RDX: 0000000000000000 RSI: 0000000000000100 RDI: ffff8881ea09ad00
RBP: ffff87fffffffa68 R08: ffff87fffffffe98 R09: ffffffff89e5bf48
R10: ffff8880708c4f08 R11: ffff8880708c4680 R12: ffff8881d35b06c0
R13: ffff88800017ad90 R14: ffff8880708c4680 R15: ffff88820a7e9940
FS:  0000000000000000(0000) GS:ffff8880aed00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff87fffffffe98 CR3: 000000020e0b5000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 exit_mm kernel/exit.c:544 [inline]
 do_exit+0x934/0x2ae0 kernel/exit.c:845
 do_group_exit+0x100/0x2e0 kernel/exit.c:955
 SYSC_exit_group kernel/exit.c:966 [inline]
 SyS_exit_group+0x19/0x20 kernel/exit.c:964
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45ca29
RSP: 002b:00007ffe4b64f608 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 000000000045ca29
RDX: 0000000000416621 RSI: fffffffffffffff7 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000080682160 R09: 00007ffe4b64f660
R10: 000000008068215c R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe4b64f660 R14: 0000000000000000 R15: 00007ffe4b64f670
Code: a8 68 fa ff ff 49 39 c5 0f 84 f7 fe ff ff e8 23 f8 23 00 4c 8d 85 30 04 00 00 4c 89 c0 48 c1 e8 03 80 3c 18 00 0f 85 df 00 00 00 <4c> 8b bd 30 04 00 00 4d 39 e7 75 95 e9 55 fd ff ff e8 f5 f7 23 
RIP: mm_update_next_owner+0x3e5/0x5b0 kernel/exit.c:452 RSP: ffff8881c16ffd48
CR2: ffff87fffffffe98
---[ end trace ff899e2e2d12baef ]---

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/05/27 23:43 linux-4.14.y 4f68020fef1c 9072c126 .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.