linux-next build error (25)

Status: closed as invalid on 2026/04/21 13:56
Reported-by: syzbot+3e8b0c8d4773f0d46956@syzkaller.appspotmail.com
First crash: 212d, last: 211d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (25) 0 (2) 2026/04/21 13:56
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 367d 466d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 835d 836d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2463d 2467d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 569d 609d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2145d 2145d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3232d 3232d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 313d 355d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3233d 3233d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1213d 1214d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 676d 709d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1937d 2035d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 83 22d 130d 27/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1619d 1621d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2609d 2609d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1364d 1417d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (21) -1 3 549d 549d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 629d 632d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 356d 356d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2347d 2411d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 3014d 3015d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2218d 2290d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1079d 1080d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2523d 2523d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2316d 2316d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2598d 2607d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
error[E0405]: cannot find trait `AlwaysRefCounted` in module `$crate::types`
error[E0277]: the trait bound `Object<T>: AlwaysRefCounted` is not satisfied

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/03/27 14:07 linux-next e77a5a5cfe43 74a13a23 .config console log report ci-upstream-rust-kasan-gce linux-next build error
2026/03/27 01:31 linux-next e77a5a5cfe43 50cdcaa1 .config console log report ci-upstream-rust-kasan-gce linux-next build error
2026/03/26 16:54 linux-next e77a5a5cfe43 fca8d360 .config console log report ci-upstream-rust-kasan-gce linux-next build error
* Struck through repros no longer work on HEAD.