syzbot


bpf-next build error (5)

Status: auto-obsoleted due to no activity on 2023/04/27 22:23
Reported-by: syzbot+cb02a28d8c55b86bb096@syzkaller.appspotmail.com
First crash: 426d, last: 426d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] bpf-next build error (5) 0 (1) 2023/01/01 22:28
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream bpf-next build error 1 2156d 2156d 0/26 closed as invalid on 2018/04/03 20:00
upstream bpf-next build error (4) bpf net 2 585d 585d 0/26 auto-obsoleted due to no activity on 2022/11/19 11:25
upstream bpf-next build error (2) 1 2147d 2147d 0/26 closed as invalid on 2018/06/14 06:16
upstream bpf-next build error (3) kernel 10 896d 1067d 20/26 fixed on 2021/11/10 00:50

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

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/12/28 22:23 bpf-next 07453245620c 44712fbc .config console log report ci-upstream-bpf-next-kasan-gce bpf-next build error
* Struck through repros no longer work on HEAD.