syzbot


linux-next build error (24)

Status: closed as invalid on 2025/12/17 13:51
Reported-by: syzbot+c78a89917a1b7c0fa4c6@syzkaller.appspotmail.com
First crash: 188d, last: 146d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (24) 1 (3) 2025/12/17 13:51
Similar bugs (24)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 200d 300d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 668d 669d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2297d 2301d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 402d 442d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 1979d 1979d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3066d 3066d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error -1 1 3066d 3066d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1046d 1047d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 509d 542d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1770d 1869d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme -1 5 1452d 1455d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2443d 2443d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1197d 1250d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 45d 46d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 382d 383d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 462d 466d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 189d 189d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2180d 2245d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2848d 2849d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2051d 2124d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 912d 913d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2356d 2356d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2149d 2149d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2431d 2441d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "64" "ARCH=x86_64" "LLVM=1" "bzImage"]: exit status 2

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/16 02:10 linux-next 563c8dd425b5 d6526ea3 .config console log report ci-upstream-rust-kasan-gce linux-next build error
2025/12/16 01:59 linux-next 563c8dd425b5 d6526ea3 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/11/03 23:36 linux-next 982312090977 686bf657 .config console log report ci-upstream-rust-kasan-gce linux-next build error
* Struck through repros no longer work on HEAD.