syzbot


linux-next build error (19)

Status: closed as invalid on 2025/02/03 14:29
Reported-by: syzbot+62ba359e1dfec1473c57@syzkaller.appspotmail.com
First crash: 48d, last: 45d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (19) 2 (3) 2025/02/03 14:29
Similar bugs (19)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (17) 2 251d 251d 0/28 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel 7 1879d 1883d 15/28 fixed on 2020/03/11 20:34
upstream linux-next build error (20) 45 10h41m 25d 0/28 upstream: reported on 2025/02/23 06:02
upstream linux-next build error (11) 2 1561d 1561d 0/28 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) 1 2648d 2648d 0/28 closed as invalid on 2017/12/18 14:32
upstream linux-next build error 1 2649d 2649d 0/28 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs 2 629d 630d 0/28 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) 28 92d 124d 0/28 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) 63 1353d 1451d 20/28 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme 5 1035d 1037d 0/28 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) 1 2025d 2025d 0/28 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) 5 780d 833d 0/28 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (8) 4 1763d 1827d 2/28 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) 4 2430d 2431d 0/28 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k 18 1634d 1706d 0/28 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto 12 495d 496d 0/28 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) 1 1939d 1939d 0/28 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel 1 1731d 1731d 0/28 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel 13 2014d 2023d 0/28 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.