syzbot


SYZFAIL: bad thread state in completion

Status: auto-closed as invalid on 2022/08/15 04:43
Reported-by: syzbot+2069ef41db89ba14a0c0@syzkaller.appspotmail.com
First crash: 960d, last: 960d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream SYZFAIL: bad thread state in completion 1 1310d 1310d 0/28 auto-closed as invalid on 2021/07/31 03:50
upstream SYZFAIL: bad thread state in completion (2) 1 1216d 1216d 0/28 auto-closed as invalid on 2021/11/01 16:42
linux-4.19 SYZFAIL: bad thread state in completion syz error 1 1161d 1371d 0/1 upstream: reported syz repro on 2021/03/01 17:42
android-5-10 SYZFAIL: bad thread state in completion syz error error 5 722d 1064d 0/2 auto-obsoleted due to no activity on 2024/10/11 00:40
linux-4.14 SYZFAIL: bad thread state in completion syz error 2 974d 1378d 0/1 upstream: reported syz repro on 2021/02/23 06:04

Sample crash report:
2022/04/17 04:42:29 executor 2 failed 11 times:
executor 2: exit status 67
SYZFAIL: bad thread state in completion
ready=1 done=1 executing=1 (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/04/17 04:42 android12-5.4 b730087e9a5d 8bcc32a6 .config console log report info ci2-android-5-4-kasan SYZFAIL: bad thread state in completion
* Struck through repros no longer work on HEAD.