linux-next build error (24)

Status: closed as invalid on 2025/12/17 13:51
Reported-by: syzbot+c78a89917a1b7c0fa4c6@syzkaller.appspotmail.com
First crash: 353d, last: 311d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (24) 1 (3) 2025/12/17 13:51
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 365d 464d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 833d 834d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2461d 2465d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 567d 607d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2143d 2143d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3230d 3230d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error -1 1 3231d 3231d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1211d 1212d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 674d 707d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1935d 2033d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 83 20d 128d 27/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1617d 1619d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2607d 2607d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1362d 1415d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 209d 210d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 547d 547d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 627d 630d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 354d 354d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2345d 2409d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 3012d 3013d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2216d 2288d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1077d 1078d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2521d 2521d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2314d 2314d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2596d 2605d 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.