syzbot


SYZFAIL: bad thread state in schedule

Status: auto-closed as invalid on 2022/04/15 20:44
Reported-by: syzbot+cb6fa9bad26b865f3540@syzkaller.appspotmail.com
First crash: 831d, last: 831d

Sample crash report:
2200/08/26 04:33:59 executor 2 failed 11 times:
executor 2: exit status 67
SYZFAIL: bad thread state in schedule
ready=0 done=0 executing=0 (errno 11: Resource temporarily unavailable)
SYZFAIL: child failed
 (errno 0: Success)
loop exited with status 67

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/01/15 20:38 android12-5.10-lts d605f2f30d54 723cfaf0 .config console log report info ci2-android-5-10 SYZFAIL: bad thread state in schedule
* Struck through repros no longer work on HEAD.