syzbot

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

linux-next build error (20)

Status: upstream: reported on 2025/02/23 06:02
Reported-by: syzbot+06fd1a3613c50d36129e@syzkaller.appspotmail.com
First crash: 4d06h, last: 1d11h
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (20) 0 (1) 2025/02/23 06:02
▶ ▼ Similar bugs (19)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (17) 2 226d 227d 0/28 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel 7 1854d 1858d 15/28 fixed on 2020/03/11 20:34
upstream linux-next build error (11) 2 1536d 1536d 0/28 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) 1 2623d 2623d 0/28 closed as invalid on 2017/12/18 14:32
upstream linux-next build error 1 2624d 2624d 0/28 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs 2 604d 605d 0/28 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) 28 67d 100d 0/28 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) 63 1328d 1426d 20/28 fixed on 2021/11/10 00:50
upstream linux-next build error (13) nvme 5 1010d 1013d 0/28 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) 1 2000d 2000d 0/28 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) 5 755d 808d 0/28 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (19) 7 20d 23d 0/28 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (8) 4 1738d 1802d 2/28 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) 4 2406d 2407d 0/28 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k 18 1609d 1681d 0/28 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto 12 470d 471d 0/28 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) 1 1914d 1914d 0/28 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel 1 1707d 1707d 0/28 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel 13 1989d 1998d 0/28 closed as invalid on 2019/09/19 05:32

Sample crash report:
<stdin>:4:15: error: use of undeclared identifier '__ref_stack_chk_guard'

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/22 01:11 linux-next d4b0fd87ff0d d34966d1 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/21 06:33 linux-next d4b0fd87ff0d 0808a665 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/21 01:12 linux-next 50a0c754714a 0808a665 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/20 07:37 linux-next 50a0c754714a 50668798 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/20 06:33 linux-next 50a0c754714a cbd8edab .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/19 14:46 linux-next 8936cec5cb6e cbd8edab .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2025/02/19 05:51 linux-next 8936cec5cb6e 9a14138f .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.