syzbot

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

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: 1047d, last: 1044d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (13) 1 (2) 2022/05/18 05:33
▶ ▼ Similar bugs (19)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (17) 2 260d 261d 0/28 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel 7 1889d 1893d 15/28 fixed on 2020/03/11 20:34
upstream linux-next build error (20) 51 5d22h 34d 0/28 upstream: reported on 2025/02/23 06:02
upstream linux-next build error (11) 2 1571d 1571d 0/28 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) 1 2658d 2658d 0/28 closed as invalid on 2017/12/18 14:32
upstream linux-next build error 1 2658d 2658d 0/28 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs 2 639d 639d 0/28 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) 28 101d 134d 0/28 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) 63 1362d 1461d 20/28 fixed on 2021/11/10 00:50
upstream linux-next build error (4) 1 2035d 2035d 0/28 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) 5 789d 842d 0/28 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (19) 7 54d 58d 0/28 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (8) 4 1772d 1837d 2/28 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) 4 2440d 2441d 0/28 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k 18 1643d 1716d 0/28 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto 12 504d 505d 0/28 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) 1 1948d 1948d 0/28 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel 1 1741d 1741d 0/28 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel 13 2024d 2033d 0/28 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.