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

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

Status: closed as invalid on 2021/05/17 11:23
Reported-by: syzbot+f9386e897a8781058604@syzkaller.appspotmail.com
First crash: 1474d, last: 1474d

▶ ▼ Discussions (1)

Title	Replies (including bot)	Last reply
[syzbot] net-next boot error: can't ssh into the instance (4)	1 (2)	2021/05/17 11:22

▶ ▼ Similar bugs (5)

Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	net-next boot error: can't ssh into the instance (3)				2	1798d	1896d	0/28	auto-closed as invalid on 2020/09/25 01:22
upstream	net-next boot error: can't ssh into the instance (2)				2	2094d	2106d	0/28	auto-closed as invalid on 2019/11/04 04:41
upstream	net-next boot error: can't ssh into the instance (6)				1	398d	398d	0/28	closed as invalid on 2024/03/27 09:32
upstream	net-next boot error: can't ssh into the instance				33	2282d	2284d	11/28	fixed on 2019/03/06 07:43
upstream	net-next boot error: can't ssh into the instance (5)				1	741d	741d	0/28	auto-obsoleted due to no activity on 2023/07/18 18:50

Crashes (3):
Time	Kernel	Commit	Syzkaller	Config	Log	Report	Syz repro	C repro	VM info	Assets (help?)	Manager	Title
2021/04/16 13:02	net-next-old	392c36e5be1d	7e2b734b	.config	console log						ci-upstream-net-kasan-gce	net-next boot error: can't ssh into the instance
2021/04/16 13:02	net-next-old	392c36e5be1d	7e2b734b	.config	console log						ci-upstream-net-kasan-gce	net-next boot error: can't ssh into the instance
2021/04/16 13:02	net-next-old	392c36e5be1d	7e2b734b	.config	console log						ci-upstream-net-kasan-gce	net-next boot error: can't ssh into the instance

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