syzbot

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

linux-next build error (14)

Status: auto-obsoleted due to no activity on 2023/03/31 06:03
Reported-by: syzbot+5301015e05ed3b325b0d@syzkaller.appspotmail.com
First crash: 895d, last: 843d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (14) 0 (1) 2022/12/08 08:48
▶ ▼ Similar bugs (20)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (17) 2 314d 314d 0/28 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel 7 1942d 1946d 15/28 fixed on 2020/03/11 20:34
upstream linux-next build error (20) 53 48d 88d 0/28 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) 2 1624d 1624d 0/28 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) 1 2711d 2711d 0/28 closed as invalid on 2017/12/18 14:32
upstream linux-next build error 1 2711d 2711d 0/28 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs 2 692d 692d 0/28 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) 28 155d 187d 0/28 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) 63 1416d 1514d 20/28 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme 5 1098d 1100d 0/28 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) 1 2088d 2088d 0/28 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (21) 3 28d 28d 0/28 upstream: reported on 2025/04/23 11:33
upstream linux-next build error (19) 7 108d 111d 0/28 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (8) 4 1826d 1890d 2/28 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) 4 2493d 2494d 0/28 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k 18 1696d 1769d 0/28 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto 12 558d 559d 0/28 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) 1 2001d 2001d 0/28 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel 1 1794d 1794d 0/28 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel 13 2077d 2086d 0/28 closed as invalid on 2019/09/19 05:32

Sample crash report:
failed to run ["make" "-j" "64" "ARCH=x86_64" "bzImage"]: exit status 2

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/30 06:03 linux-next ae0c77e1bc69 9dfcf09c .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2023/01/23 04:43 linux-next 691781f561e9 559a440a .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/12/09 13:20 linux-next f925116b24c0 67be1ae7 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/12/08 09:06 linux-next f925116b24c0 1034e5fa .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2022/12/08 08:33 linux-next f925116b24c0 d88f3abb .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.