upstream test error: BUG: got no fallback coverage:

Status: closed as invalid on 2021/02/10 11:20
Reported-by: syzbot+e6ca682acbbf21043787@syzkaller.appspotmail.com
First crash: 2037d, last: 2037d
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
upstream test error: BUG: got no fallback coverage: 1 (2) 2021/02/10 11:20
▶ ▼ Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream upstream test error: BUG: got no fallback coverage: (2) -1 50 1728d 2015d 0/29 auto-closed as invalid on 2022/03/05 19:48

Sample crash report:
1970/01/01 00:02:05 connecting to host at 10.0.2.10:40353
1970/01/01 00:02:05 checking machine...
1970/01/01 00:02:05 checking revisions...
ps_root_recvmsgcb: failed to send message to pid 4476: Connection refused
1970/01/01 00:02:05 testing simple program...
1970/01/01 00:02:08 BUG: got no fallback coverage:
loop exited with status 11
ps_root_recvmsgcb: failed to send message to pid 4508: Connection refused
ps_root_recvmsgcb: failed to send message to pid 4544: Connection refused
ps_root_recvmsgcb: failed to send message to pid 4543: Connection refused
ps_bpf_start_bpf: bpf_open: Invalid argument
ps_root_recvmsg: Invalid argument
ps_bpf_start_bpf: bpf_open: Invalid argument
ps_root_recvmsg: Invalid argument
ps_bpf_start_bpf: bpf_open: Invalid argument
ps_root_recvmsg: Invalid argument

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/01/31 09:41 upstream 6642d600b541 fc9fd31e .config console log report ci-qemu2-arm64-mte upstream test error: BUG: got no fallback coverage:
* Struck through repros no longer work on HEAD.