bpf-next build error (7)

Status: closed as invalid on 2026/08/28 12:35
First crash: 49d, last: 49d
▶ ▼ Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream bpf-next build error -1 1 3117d 3117d 0/29 closed as invalid on 2018/04/03 20:00
upstream bpf-next build error (4) bpf net -1 2 1546d 1546d 0/29 auto-obsoleted due to no activity on 2022/11/19 11:25
upstream bpf-next build error (8) prio:low -1 2 23d 39d 0/29 upstream: reported on 2026/09/07 07:55
upstream bpf-next build error (5) -1 1 1387d 1383d 0/29 auto-obsoleted due to no activity on 2023/04/27 22:23
upstream bpf-next build error (2) -1 1 3108d 3108d 0/29 closed as invalid on 2018/06/14 06:16
upstream bpf-next build error (6) -1 3 844d 927d 0/29 auto-obsoleted due to no activity on 2024/10/01 18:55
upstream bpf-next build error (3) kernel -1 10 1857d 2028d 20/29 fixed on 2021/11/10 00:50

Sample crash report:
failed to run ["make" "KERNELVERSION=syzkaller" "KERNELRELEASE=syzkaller" "LOCALVERSION=-syzkaller" "-j" "64" "ARCH=x86_64" "LLVM=1" "bzImage"]: exit status 2

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/08/28 00:54 bpf-next 5e875ae9e9ff e2fa417d .config console log report ci-upstream-bpf-next-kasan-gce bpf-next build error
* Struck through repros no longer work on HEAD.