syzbot

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

linux-next build error (19)

Status: closed as invalid on 2025/02/03 14:29
Reported-by: syzbot+62ba359e1dfec1473c57@syzkaller.appspotmail.com
First crash: 274d, last: 271d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (19) 2 (3) 2025/02/03 14:29
▶ ▼ Similar bugs (21)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 8d18h 108d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 477d 477d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2105d 2109d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 211d 250d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 1787d 1787d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 2874d 2874d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error -1 1 2874d 2874d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 855d 855d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 318d 350d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1578d 1677d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme -1 5 1261d 1263d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2251d 2251d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1005d 1058d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (21) -1 3 191d 191d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (8) -1 4 1989d 2053d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2656d 2657d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 1859d 1932d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 721d 722d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2164d 2164d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 1957d 1957d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2240d 2249d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
scripts/gendwarfksyms/gendwarfksyms.h:6:10: fatal error: dwarf.h: No such file or directory

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/03 02:21 linux-next 00f3246adeea 568559e4 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/02 08:01 linux-next df4b2bbff898 568559e4 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/01 12:32 linux-next df4b2bbff898 0dff8567 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/01/31 17:21 linux-next df4b2bbff898 aa47157c .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/01/31 04:28 linux-next df4b2bbff898 4c6ac32f .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/01/30 23:32 linux-next a13f6e0f405e 4c6ac32f .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/01/30 13:04 linux-next a13f6e0f405e 9c8ab845 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.