linux-next build error (3)

Status: closed as invalid on 2018/07/24 13:58
Reported-by: syzbot+9118f0a7ae77f4eee4a9@syzkaller.appspotmail.com
First crash: 3000d, last: 2999d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
linux-next build error (3) 3 (4) 2018/07/24 11:55
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 351d 451d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 819d 820d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2448d 2452d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 554d 593d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2130d 2130d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3217d 3217d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 297d 339d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3217d 3217d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1197d 1198d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 660d 693d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1921d 2020d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 83 7d04h 114d 27/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1603d 1606d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2594d 2594d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1348d 1401d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 196d 197d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 533d 534d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 613d 617d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 340d 340d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2331d 2396d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (10) ath11k -1 18 2202d 2275d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1063d 1064d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2507d 2507d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2300d 2300d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2583d 2592d 0/29 closed as invalid on 2019/09/19 05:32
Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/07/24 11:37 linux-next 3946cd385042 4969639c console log ci-upstream-linux-next-kasan-gce-root
2018/07/24 07:25 linux-next 3946cd385042 912c93d7 console log ci-upstream-linux-next-kasan-gce-root
2018/07/23 20:02 linux-next 6d93abaf4c5b 912c93d7 console log ci-upstream-linux-next-kasan-gce-root
2018/07/23 10:22 linux-next 6d93abaf4c5b f69c5fcd console log ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.