syzbot


gvisor test error: lost connection to test machine (4)

Status: closed as invalid on 2020/09/13 08:17
Reported-by: syzbot+a89e876679b88697eb4a@syzkaller.appspotmail.com
First crash: 1606d, last: 1606d
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor gvisor test error: lost connection to test machine (5) 1350 1292d 1494d 0/26 auto-closed as invalid on 2021/07/13 14:39
gvisor gvisor test error: lost connection to test machine (9) 1 140d 133d 0/26 auto-obsoleted due to no activity on 2024/10/07 08:04
gvisor gvisor test error: lost connection to test machine (3) 187 1694d 1700d 0/26 closed as invalid on 2020/04/08 10:30
gvisor gvisor test error: lost connection to test machine (2) 225 1809d 2083d 0/26 auto-closed as invalid on 2020/03/13 01:01
gvisor gvisor test error: lost connection to test machine (6) 1 1054d 1054d 0/26 closed as invalid on 2022/01/07 14:19
gvisor gvisor test error: lost connection to test machine 160 2331d 2345d 0/26 closed as invalid on 2018/12/12 10:27
gvisor gvisor test error: lost connection to test machine (7) 12 998d 1010d 0/26 auto-closed as invalid on 2022/06/01 21:37
Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/07/04 01:16 gvisor 418db67e2fa1 695ef2dd .config console log ci-gvisor-kvm-direct-sandbox
* Struck through repros no longer work on HEAD.