syzbot


linux-next build error (25)

Status: upstream: reported on 2026/03/26 16:56
Reported-by: syzbot+3e8b0c8d4773f0d46956@syzkaller.appspotmail.com
First crash: 19d, last: 18d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (25) 0 (1) 2026/03/26 16:56
Similar bugs (24)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 174d 274d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 642d 643d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2270d 2275d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 376d 416d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 1952d 1952d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3039d 3039d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 120d 162d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3040d 3040d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1020d 1021d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 483d 516d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1744d 1843d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme -1 5 1426d 1429d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2417d 2416d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1171d 1224d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (21) -1 3 356d 357d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 436d 440d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 163d 163d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2154d 2218d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2822d 2823d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2025d 2097d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 886d 887d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2330d 2330d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2123d 2123d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2405d 2414d 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.