linux-next build error (15)

Status: auto-obsoleted due to no activity on 2023/08/28 20:53
Subsystems: cifs
[Documentation on labels]
Reported-by: syzbot+4c222134dc629d256ee8@syzkaller.appspotmail.com
First crash: 1184d, last: 1184d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] linux-next build error (15) 0 (1) 2023/06/29 06:23
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 337d 437d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 805d 806d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2434d 2438d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 540d 579d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2116d 2116d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3203d 3203d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 283d 325d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3203d 3203d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (18) -1 28 646d 679d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1907d 2006d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 78 1d14h 101d 23/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1589d 1592d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2580d 2580d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1334d 1387d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 182d 183d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 519d 520d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 599d 603d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 326d 326d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (8) -1 4 2317d 2382d 2/29 closed as invalid on 2020/05/27 06:38
upstream linux-next build error (3) -1 4 2985d 2986d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2188d 2261d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1049d 1050d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2493d 2493d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2286d 2286d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2569d 2578d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
fs/smb/client/cifs_debug.c:169:1: error: label at end of compound statement

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/29 20:52 linux-next 8b14b70331aa 7b33cf8f .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
2023/06/29 05:52 linux-next 8b14b70331aa ca69c785 .config console log report ci-upstream-linux-next-kasan-gce-root linux-next build error
* Struck through repros no longer work on HEAD.