syzbot

 sign-in | mailing list | source | docs
🐞 Open [1651]
≡ Subsystems
🐞 Fixed [6000]
🐞 Invalid [14793]
⬇ Missing Backports [135]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

bpf-next test error: BUG: mismatching fuzzer/executor system call descriptions: ADDR vs ADDR

Status: closed as invalid on 2020/03/31 14:00
First crash: 1763d, last: 1763d

Sample crash report:
Warning: Permanently added '10.128.1.36' (ECDSA) to the list of known hosts.
2020/03/31 13:35:23 fuzzer started
2020/03/31 13:35:25 connecting to host at 10.128.0.26:44443
2020/03/31 13:35:25 checking machine...
2020/03/31 13:35:25 checking revisions...
2020/03/31 13:35:25 BUG: mismatching fuzzer/executor system call descriptions: 670a1e865c0bc7d60e9886acf4666ee3677e346e vs f787d115f9efa49fdd59261850f5c05f43fbe327
syzkaller login:

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/03/31 13:35 bpf-next 3902baf9abfa 46105100 .config console log report ci-upstream-bpf-next-kasan-gce
2020/03/31 13:35 bpf-next 3902baf9abfa 46105100 .config console log report ci-upstream-bpf-next-kasan-gce
2020/03/31 13:35 bpf-next 3902baf9abfa 46105100 .config console log report ci-upstream-bpf-next-kasan-gce
* Struck through repros no longer work on HEAD.