linux-next build error (8)

Status: closed as invalid on 2020/05/27 06:38
Reported-by: syzbot+792dec47d693ccdc05a0@syzkaller.appspotmail.com
Fix commit: e21408ceec2d rcu-tasks: Add RCU tasks to rcutorture writer stall output
First crash: 2371d, last: 2307d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
linux-next build error (8) 10 (11) 2020/03/20 17:04
▶ ▼ Similar bugs (25)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next build error (22) -1 27 327d 427d 0/29 closed as invalid on 2025/10/23 12:06
upstream linux-next build error (17) -1 2 795d 796d 0/29 auto-obsoleted due to no activity on 2024/09/10 01:54
upstream linux-next build error (7) kernel -1 7 2423d 2428d 15/29 fixed on 2020/03/11 20:34
upstream linux-next build error (20) -1 53 529d 569d 0/29 closed as invalid on 2025/04/14 14:48
upstream linux-next build error (11) -1 2 2105d 2105d 0/29 auto-closed as invalid on 2021/02/07 17:19
upstream linux-next build error (2) -1 1 3192d 3192d 0/29 closed as invalid on 2017/12/18 14:32
upstream linux-next build error (24) -1 3 273d 315d 0/29 closed as invalid on 2025/12/17 13:51
upstream linux-next build error -1 1 3193d 3193d 0/29 closed as invalid on 2017/12/18 08:32
upstream linux-next build error (15) cifs -1 2 1173d 1174d 0/29 auto-obsoleted due to no activity on 2023/08/28 20:53
upstream linux-next build error (18) -1 28 636d 669d 0/29 auto-obsoleted due to no activity on 2025/01/27 03:08
upstream linux-next build error (12) -1 63 1897d 1996d 20/29 fixed on 2021/11/10 00:50
upstream linux-next build error (26) -1 62 5h18m 90d 22/29 upstream: reported on 2026/06/16 20:06
upstream linux-next build error (13) nvme -1 5 1579d 1582d 0/29 auto-closed as invalid on 2022/07/18 23:22
upstream linux-next build error (4) -1 1 2570d 2569d 0/29 closed as invalid on 2019/09/02 13:57
upstream linux-next build error (14) -1 5 1324d 1377d 0/29 auto-obsoleted due to no activity on 2023/03/31 06:03
upstream linux-next build error (25) -1 3 171d 172d 0/29 closed as invalid on 2026/04/21 13:56
upstream linux-next build error (21) -1 3 509d 510d 0/29 auto-obsoleted due to no activity on 2025/06/23 00:33
upstream linux-next build error (19) -1 7 589d 593d 0/29 closed as invalid on 2025/02/03 14:29
upstream linux-next build error (23) -1 1 316d 316d 0/29 closed as invalid on 2025/11/03 14:34
upstream linux-next build error (3) -1 4 2975d 2976d 0/29 closed as invalid on 2018/07/24 13:58
upstream linux-next build error (10) ath11k -1 18 2178d 2250d 0/29 auto-closed as invalid on 2020/11/27 07:58
upstream linux-next build error (16) crypto -1 12 1039d 1040d 0/29 auto-obsoleted due to no activity on 2023/12/21 01:05
upstream linux-next build error (6) -1 1 2483d 2483d 0/29 closed as invalid on 2019/11/28 08:37
upstream linux-next build error (9) kernel -1 1 2276d 2276d 0/29 closed as invalid on 2020/06/22 13:12
upstream linux-next build error (5) kernel -1 13 2558d 2567d 0/29 closed as invalid on 2019/09/19 05:32

Sample crash report:
gcc: fatal error: Killed signal terminated program cc1

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/05/22 01:23 linux-next e8f3274774b4 5afa2ddd .config console log report ci-upstream-linux-next-kasan-gce-root
2020/05/21 15:01 linux-next e8f3274774b4 1f30020f .config console log report ci-upstream-linux-next-kasan-gce-root
2020/05/19 18:24 linux-next fb57b1fabcb2 6d882fd2 .config console log report ci-upstream-linux-next-kasan-gce-root
2020/03/18 16:19 linux-next 47780d7892b7 0a96a13c .config console log report ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.