syzbot


BUG: unable to handle kernel paging request in __schedule

Status: fixed on 2018/01/03 02:35
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+265d05dfcc11f25e88c91edbe61d813b79d9d0ac@syzkaller.appspotmail.com
Fix commit: 7fb983b4dd56 x86/entry: Fix assumptions that the HW TSS is at the beginning of cpu_tss
First crash: 2385d, last: 2383d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KMSAN: uninit-value in __schedule (5) kernel 5 7d12h 64d 0/28 upstream: reported on 2024/04/10 09:12
android-54 BUG: unable to handle kernel paging request in __schedule C 12 1204d 1361d 0/2 auto-obsoleted due to no activity on 2023/04/17 21:57

Sample crash report:
netlink: 8 bytes leftover after parsing attributes in process `syz-executor3'.
BUG: unable to handle kernel paging request at 00000000fe8ee0e9
IP: __schedule+0x5ae/0x2060 kernel/sched/core.c:3371
PGD 5e28067 P4D 5e28067 PUD 5e2a067 PMD 0 
Oops: 0002 [#1] SMP KASAN
Dumping ftrace buffer:
   (ftrace buffer empty)
Modules linked in:
CPU: 1 PID: 10712 Comm: syz-executor7 Not tainted 4.15.0-rc2-next-20171204+ #58
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: 000000008dff00dd task.stack: 00000000eb7008ea
RIP: 0010:__schedule+0x5ae/0x2060 kernel/sched/core.c:3371
RSP: 0018:ffff880196bf7ac0 EFLAGS: 00010006
RAX: ffff8801d5aec860 RBX: ffff8801db527900 RCX: 0000000000000000
RDX: 1ffff1003ab5d90c RSI: ffff8801db528398 RDI: ffff8801db5279a0
RBP: ffff880196bf7c90 R08: ffff8801d5aec330 R09: ffff8801cd6ce598
R10: 1ffff10039d23065 R11: ffff8801d5aec300 R12: ffff8801cd2c2540
R13: 0000000000027900 R14: ffff880196bf0000 R15: ffff8801d5aec240
FS:  00007f0c59b32700(0000) GS:ffff8801db500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffffffffff8 CR3: 00000001c2a48000 CR4: 00000000001426e0
Call Trace:
 schedule+0xf5/0x430 kernel/sched/core.c:3435
 exit_to_usermode_loop+0x1d1/0x310 arch/x86/entry/common.c:151
 prepare_exit_to_usermode arch/x86/entry/common.c:195 [inline]
 syscall_return_slowpath+0x490/0x550 arch/x86/entry/common.c:264
 entry_SYSCALL_64_fastpath+0x94/0x96
RIP: 0033:0x452867
RSP: 002b:00007f0c59b30078 EFLAGS: 00000202 ORIG_RAX: 0000000000000010
RAX: 0000000000000000 RBX: 0000000020008000 RCX: 0000000000452867
RDX: 00007f0c59b306d0 RSI: 000000004138ae84 RDI: 000000000000001c
RBP: 0000000020008800 R08: 6c9121c2c4e0230f R09: e0200f007e360ff7
R10: e0220f0000400035 R11: 0000000000000202 R12: 000000000000001d
R13: 0000000020007000 R14: 00007f0c59b326d4 R15: 0000000000000000
Code: ff 48 b8 00 00 00 00 00 fc ff df 4c 89 a3 e8 09 00 00 48 c1 ea 03 80 3c 02 00 0f 85 7e 15 00 00 48 8b 85 60 fe ff ff 48 83 00 01 <cc> 1f 44 00 00 65 8b 05 86 5f ea 7a 89 c0 48 0f a3 05 cc f5 47 
RIP: __schedule+0x5ae/0x2060 kernel/sched/core.c:3371 RSP: ffff880196bf7ac0
CR2: fffffffffffffff8
---[ end trace d9ceca83b0fe41f3 ]---
Kernel panic - not syncing: Fatal exception
Dumping ftrace buffer:
   (ftrace buffer empty)
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2017/12/04 11:39 linux-next 7cc61a0a562c 48359b97 .config console log report ci-upstream-next-kasan-gce
2017/12/02 16:44 mmots 4131d5166185 29b0fd90 .config console log report ci-upstream-mmots-kasan-gce
* Struck through repros no longer work on HEAD.