syzbot


linux-next build error (13)

Status: auto-closed as invalid on 2022/07/18 23:22
Subsystems: nvme
[Documentation on labels]
Reported-by: syzbot+7013da477748d0b624b9@syzkaller.appspotmail.com
First crash: 1260d, last: 1258d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (13) 1 (2) 2022/05/18 05:33
Similar bugs (21)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 5d22h 105d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 474d 474d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2102d 2106d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 208d 248d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 1784d 1784d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 2871d 2871d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error -1 1 2872d 2872d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 852d 853d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 315d 347d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1576d 1674d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (4) -1 1 2248d 2248d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1003d 1055d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (21) -1 3 188d 188d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 268d 271d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (8) -1 4 1986d 2050d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2653d 2654d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 1857d 1929d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 718d 719d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2162d 2161d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 1954d 1954d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2237d 2246d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
drivers/nvme/host/fc.c:1914: undefined reference to `blkcg_get_fc_appid'

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/05/19 23:21 linux-next 21498d01d045 cb1ac2e7 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/05/19 11:17 linux-next 21498d01d045 50c53f39 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/05/18 13:34 linux-next 736ee37e2e8e 50c53f39 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/05/18 10:38 linux-next 736ee37e2e8e 744a39e2 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/05/17 11:21 linux-next 47c1c54d1bcd 744a39e2 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.