linux-next build error (21)

Status: auto-obsoleted due to no activity on 2025/06/23 00:33
Reported-by: syzbot+19396db90a543f153fad@syzkaller.appspotmail.com
First crash: 475d, last: 474d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (21) 0 (1) 2025/04/23 11:33
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 292d 392d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 760d 761d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2389d 2393d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 494d 534d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2071d 2071d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3158d 3158d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 238d 280d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3158d 3158d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1138d 1139d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 601d 634d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1862d 1961d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 43 5d01h 55d 1/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1544d 1547d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2535d 2535d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1289d 1342d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 137d 138d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (19) -1 7 554d 558d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 281d 281d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2272d 2337d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2940d 2941d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2143d 2216d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1004d 1005d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2448d 2448d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2241d 2241d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2523d 2533d 0/29 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.