linux-next build error (6)

Status: closed as invalid on 2019/11/28 08:37
Reported-by: syzbot+88f3974342fd0f011404@syzkaller.appspotmail.com
First crash: 2485d, last: 2485d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
linux-next build error (6) 1 (2) 2019/11/28 08:37
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 329d 429d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 797d 798d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2425d 2430d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 531d 571d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2107d 2107d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3195d 3195d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 275d 317d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3195d 3195d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1175d 1176d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 638d 671d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1899d 1998d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 66 21h16m 92d 22/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1581d 1584d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2572d 2572d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1326d 1379d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 174d 174d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 511d 512d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 591d 595d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 318d 318d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2309d 2373d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2977d 2978d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2180d 2253d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1041d 1042d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (9) kernel -1 1 2278d 2278d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2560d 2570d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
failed to run ["make" "bzImage" "CC=/syzkaller/gcc/bin/gcc" "-j64"]: exit status 2

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/11/28 07:03 linux-next d26b0e226f22 0d63f89c .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.