linux-next build error (14)

Status: auto-obsoleted due to no activity on 2023/03/31 06:03
Reported-by: syzbot+5301015e05ed3b325b0d@syzkaller.appspotmail.com
First crash: 1334d, last: 1281d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (14) 0 (1) 2022/12/08 08:48
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 284d 384d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 753d 753d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2381d 2385d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 487d 526d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2063d 2063d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3150d 3150d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 231d 272d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3150d 3150d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1131d 1131d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 594d 626d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1854d 1953d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 37 8h29m 48d 0/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1537d 1539d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2527d 2527d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (25) -1 3 129d 130d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 467d 467d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 547d 550d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 273d 273d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2265d 2329d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2932d 2933d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2135d 2208d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 997d 998d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2440d 2440d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2233d 2233d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2516d 2525d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
failed to run ["make" "-j" "64" "ARCH=x86_64" "bzImage"]: exit status 2

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/30 06:03 linux-next ae0c77e1bc69 9dfcf09c .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2023/01/23 04:43 linux-next 691781f561e9 559a440a .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/12/09 13:20 linux-next f925116b24c0 67be1ae7 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/12/08 09:06 linux-next f925116b24c0 1034e5fa .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/12/08 08:33 linux-next f925116b24c0 d88f3abb .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.