panic: trying to use inactive address space?

Status: auto-closed as invalid on 2019/10/25 08:44
Reported-by: syzbot+8d6f6c371ba575745004@syzkaller.appspotmail.com
First crash: 2675d, last: 2675d
▶ ▼ Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor panic: trying to use inactive address space? (2) 2 3 2424d 2422d 0/26 auto-closed as invalid on 2020/04/09 06:20
gvisor panic: trying to use inactive address space? (3) 2 1 2194d 2187d 0/26 auto-closed as invalid on 2020/11/25 21:12
gvisor panic: trying to use inactive address space? (4) 2 36 2030d 2028d 0/26 auto-closed as invalid on 2021/04/07 22:44

Sample crash report:
panic: trying to use inactive address space?

goroutine 501 [running]:
gvisor.googlesource.com/gvisor/pkg/sentry/mm.(*MemoryManager).AddressSpace(...)
	pkg/sentry/mm/address_space.go:31
gvisor.googlesource.com/gvisor/pkg/sentry/kernel.(*runApp).execute(0x0, 0xc0001a0000, 0x12e62e0, 0x0)
	pkg/sentry/kernel/task_run.go:210 +0x1fcd
gvisor.googlesource.com/gvisor/pkg/sentry/kernel.(*Task).run(0xc0001a0000, 0x5b)
	pkg/sentry/kernel/task_run.go:92 +0x2e6
created by gvisor.googlesource.com/gvisor/pkg/sentry/kernel.(*Task).Start
	pkg/sentry/kernel/task_start.go:286 +0x19e

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/05/04 02:56 https://gvisor.googlesource.com/gvisor master 8972e47a2edb e9039493 .config console log report ci-gvisor-kvm-direct-overlay-host-race
* Struck through repros no longer work on HEAD.