net-next boot error: can't ssh into the instance (3)

net-next boot error: can't ssh into the instance (3)

Status: auto-closed as invalid on 2020/09/25 01:22
Reported-by: syzbot+1312d700c503da6008a1@syzkaller.appspotmail.com
First crash: 2097d, last: 1994d

▶ ▼ Discussions (1)

Title	Replies (including bot)	Last reply
net-next boot error: can't ssh into the instance (3)	0 (1)	2020/02/19 10:27

▶ ▼ Similar bugs (5)

Kernel	Title	Rank 🛈	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	net-next boot error: can't ssh into the instance (2)	-1				2	2290d	2302d	0/29	auto-closed as invalid on 2019/11/04 04:41
upstream	net-next boot error: can't ssh into the instance (6)	-1				1	595d	595d	0/29	closed as invalid on 2024/03/27 09:32
upstream	net-next boot error: can't ssh into the instance	-1				33	2478d	2480d	11/29	fixed on 2019/03/06 07:43
upstream	net-next boot error: can't ssh into the instance (5)	-1				1	937d	937d	0/29	auto-obsoleted due to no activity on 2023/07/18 18:50
upstream	net-next boot error: can't ssh into the instance (4)	-1				3	1670d	1640d	0/29	closed as invalid on 2021/05/17 11:23

Crashes (2):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2020/05/28 01:21	net-next-old	50ce4c099beb	142a0957	.config	console log						ci-upstream-net-kasan-gce
2020/02/14 22:59	net-next-old	2019fc96af22	5d7b90f1	.config	console log						ci-upstream-net-kasan-gce

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