kmsan boot error: can't ssh into the instance: failed to run ["ssh" "-p" "22" "-i" "/syzkaller/managers/upstream-kmsan-gce/latest.tmp/key" "-F" "/dev/null" "-o" "UserKnownHostsFile=/dev/null" "-o" "Ba (2)

kmsan boot error: can't ssh into the instance: failed to run ["ssh" "-p" "22" "-i" "/syzkaller/managers/upstream-kmsan-gce/latest.tmp/key" "-F" "/dev/null" "-o" "UserKnownHostsFile=/dev/null" "-o" "Ba (2)

Status: auto-closed as invalid on 2019/06/19 13:26
First crash: 1953d, last: 1953d

▶ ▼ Similar bugs (1)

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	kmsan boot error: can't ssh into the instance: failed to run ["ssh" "-p" "22" "-i" "/syzkaller/managers/upstream-kmsan-gce/latest.tmp/key" "-F" "/dev/null" "-o" "UserKnownHostsFile=/dev/null" "-o" "Ba				12	1954d	1955d	0/26	closed as invalid on 2018/12/21 09:40

Crashes (2):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2018/12/21 13:22	https://github.com/google/kmsan.git master	ade06f5f8b47	588075e6	.config	console log						ci-upstream-kmsan-gce
2018/12/21 13:22	https://github.com/google/kmsan.git master	ade06f5f8b47	588075e6	.config	console log						ci-upstream-kmsan-gce

* ~~Struck through~~ repros no longer work on HEAD.