syzbot

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

linux-next build error (17)

Status: auto-obsoleted due to no activity on 2024/09/10 01:54
Reported-by: syzbot+96c36598b73a9d3f3e25@syzkaller.appspotmail.com
First crash: 356d, last: 355d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (17) 0 (1) 2024/07/11 09:05
▶ ▼ Similar bugs (20)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (7) kernel 7 1984d 1988d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) 53 90d 129d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) 2 1666d 1666d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) 1 2753d 2753d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error 1 2753d 2753d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs 2 734d 734d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) 28 196d 229d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) 63 1457d 1556d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme 5 1140d 1142d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) 1 2130d 2130d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) 5 884d 937d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (21) 3 70d 70d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) 7 149d 153d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (8) 4 1867d 1932d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) 4 2535d 2536d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k 18 1738d 1811d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto 12 600d 601d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) 1 2043d 2043d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel 1 1836d 1836d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel 13 2119d 2128d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
drivers/bluetooth/hci_qca.c:2501:10: error: label at end of compound statement: expected statement

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/07/12 01:53 linux-next f477dd6eede3 eaeb5c15 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2024/07/11 07:23 linux-next f477dd6eede3 c699c2eb .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.