syzbot


linux-next build error

Status: closed as invalid on 2017/12/18 08:32
Reported-by: syzbot+@syzkaller.appspotmail.com
First crash: 1818d, last: 1818d
similar bugs (13):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (7) 7 1048d 1052d 17/24 fixed on 2020/03/11 20:34
upstream linux-next build error (11) 2 730d 730d 0/24 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) 1 1817d 1817d 0/24 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (12) 63 522d 620d 22/24 fixed on 2021/11/10 00:50
upstream linux-next build error (13) 5 204d 206d 0/24 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) 1 1194d 1194d 0/24 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) 3 19h59m 2d00h 0/24 upstream: reported on 2022/12/08 08:48
upstream linux-next build error (8) 4 932d 996d 2/24 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) 4 1599d 1600d 0/24 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) 18 803d 875d 0/24 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (6) 1 1108d 1108d 0/24 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) 1 901d 900d 0/24 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) 13 1183d 1192d 0/24 closed as invalid on 2019/09/19 05:32
Crashes (1):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-next-kasan-gce 2017/12/18 06:25 linux-next 53600ecfb600 d5beb42a .config log
* Struck through repros no longer work on HEAD.