syzbot

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

linux-next build error (21)

Status: upstream: reported on 2025/04/23 11:33
Reported-by: syzbot+19396db90a543f153fad@syzkaller.appspotmail.com
First crash: 1d06h, last: 17h09m
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (21) 0 (1) 2025/04/23 11:33
▶ ▼ Similar bugs (20)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (17) 2 286d 287d 0/28 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel 7 1915d 1919d 15/28 fixed on 2020/03/11 20:34
upstream linux-next build error (20) 53 20d 60d 0/28 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) 2 1597d 1597d 0/28 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) 1 2684d 2684d 0/28 closed as invalid on 2017/12/18 14:32
upstream linux-next build error 1 2684d 2684d 0/28 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs 2 664d 665d 0/28 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) 28 127d 160d 0/28 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) 63 1388d 1487d 20/28 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme 5 1070d 1073d 0/28 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) 1 2061d 2061d 0/28 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) 5 815d 868d 0/28 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (19) 7 80d 84d 0/28 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (8) 4 1798d 1863d 2/28 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) 4 2466d 2467d 0/28 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k 18 1669d 1742d 0/28 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto 12 530d 531d 0/28 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) 1 1974d 1974d 0/28 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel 1 1767d 1767d 0/28 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel 13 2049d 2059d 0/28 closed as invalid on 2019/09/19 05:32

Sample crash report:
kernel/dma/contiguous.c:497:1: error: static assertion expression is not an integral constant expression
kernel/dma/coherent.c:410:1: error: static assertion expression is not an integral constant expression
drivers/clk/clk-fixed-factor.c:379:1: error: static assertion expression is not an integral constant expression

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/24 00:32 linux-next 6ac908f24cd7 9882047a .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/04/23 11:51 linux-next 6ac908f24cd7 d971f7e2 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/04/23 11:00 linux-next 6ac908f24cd7 53a8b9bd .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.