linux-next build error (11)

Status: auto-closed as invalid on 2021/02/07 17:19
Reported-by: syzbot+79023dbd85f19ddbe8cc@syzkaller.appspotmail.com
First crash: 2106d, last: 2106d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
linux-next build error (11) 0 (1) 2020/12/09 17:13
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 328d 427d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 796d 797d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2424d 2428d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 530d 570d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (2) -1 1 3193d 3193d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 274d 316d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3194d 3194d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1174d 1175d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 637d 670d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1898d 1996d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 64 7h49m 91d 22/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1580d 1582d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2570d 2570d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1325d 1378d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 172d 173d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 510d 510d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 590d 593d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 317d 317d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2308d 2372d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2975d 2976d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2179d 2251d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1040d 1041d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2484d 2484d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2277d 2277d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2559d 2568d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
failed to run ["make" "-j" "64" "ARCH=x86_64" "CC=/syzkaller/gcc/bin/gcc" "oldconfig"]: exit status 2

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/12/09 17:18 linux-next 2f1d5c77f13f c090b4da .config console log report ci-upstream-linux-next-kasan-gce-root
2020/12/09 16:57 linux-next 2f1d5c77f13f 40cc414d .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.