syzbot

 sign-in | mailing list | source | docs
🐞 Open [1501]
≡ Subsystems
🐞 Fixed [6533]
🐞 Invalid [16697]
⬇ Missing Backports [202]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

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: 1727d, last: 1727d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
linux-next build error (11) 0 (1) 2020/12/09 17:13
▶ ▼ Similar bugs (21)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 14 17d 48d 0/29 upstream: reported on 2025/07/15 11:51
upstream linux-next build error (17) -1 2 416d 417d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2045d 2049d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 151d 190d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (2) -1 1 2814d 2814d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error -1 1 2814d 2814d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 795d 795d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 257d 290d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1518d 1617d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme -1 5 1200d 1203d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2191d 2191d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 945d 998d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (21) -1 3 130d 131d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 210d 214d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (8) -1 4 1928d 1993d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2596d 2597d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 1799d 1872d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 660d 661d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2104d 2104d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 1897d 1897d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2180d 2189d 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.