syzbot


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: 739d, last: 738d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (17) 0 (1) 2024/07/11 09:05
Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 270d 370d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (7) kernel -1 7 2367d 2371d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 473d 512d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2049d 2049d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3136d 3136d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 216d 258d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3136d 3136d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1117d 1117d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 579d 612d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1840d 1939d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 30 18d 34d 0/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1522d 1525d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2513d 2513d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1267d 1320d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 115d 116d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 452d 453d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 532d 536d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 259d 259d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2250d 2315d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2918d 2919d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2121d 2194d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 982d 983d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2426d 2426d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2219d 2219d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2502d 2511d 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.