syzbot


panic: Sentry detected 7 stuck task(s):

Status: auto-closed as invalid on 2020/06/14 01:41
Reported-by: syzbot+d0f6d4093fb4748cd512@syzkaller.appspotmail.com
First crash: 1716d, last: 1716d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor panic: Sentry detected 7 stuck task(s): (2) 16 1538d 1594d 0/26 closed as dup on 2020/09/13 08:11

Sample crash report:
panic: Sentry detected 7 stuck task(s):
	Task tid: 6082 (0x17c2), entered RunSys state 3m38.32s ago.
	Task tid: 6084 (0x17c4), entered RunSys state 3m37.74s ago.
	Task tid: 107 (0x6b), entered RunSys state 3m38.52s ago.
	Task tid: 105 (0x69), entered RunSys state 3m38.66s ago.
	Task tid: 6083 (0x17c3), entered RunSys state 3m38.49s ago.
	Task tid: 6085 (0x17c5), entered RunSys state 3m38.65s ago.
	Task tid: 6086 (0x17c6), entered RunSys state 3m38.31s ago.
Search for '(*Task).run(0x..., 0x<tid>)' in the stack dump to find the offending goroutine
Stack for running G's are skipped while panicking.
DIAGNOSIS:
I0316 01:40:08.414200   50562 main.go:305] ***************************
I0316 01:40:08.414258   50562 main.go:306] Args: [/syzkaller/managers/kvm-direct-sandbox/current/image -root /syzkaller/managers/kvm-direct-sandbox/workdir/gvisor_root -watchdog-action=panic -network=none -debug -alsologtostderr -platform=kvm -file-access=exclusive -network=sandbox debug -stacks --ps ci-gvisor-kvm-direct-sandbox-1]
I0316 01:40:08.414304   50562 main.go:307] Version release-20200219.0-160-gf693e1334b6f
I0316 01:40:08.414325   50562 main.go:308] PID: 50562
I0316 01:40:08.414352   50562 main.go:309] UID: 0, GID: 0
I0316 01:40:08.414373   50562 main.go:310] Configuration:
I0316 01:40:08.414395   50562 main.go:311] 		RootDir: /syzkaller/managers/kvm-direct-sandbox/workdir/gvisor_root
I0316 01:40:08.414418   50562 main.go:312] 		Platform: kvm
I0316 01:40:08.414438   50562 main.go:313] 		FileAccess: exclusive, overlay: false
I0316 01:40:08.414474   50562 main.go:314] 		Network: sandbox, logging: false
I0316 01:40:08.414498   50562 main.go:315] 		Strace: false, max size: 1024, syscalls: []
I0316 01:40:08.414519   50562 main.go:316] ***************************
D0316 01:40:08.414569   50562 container.go:159] Load container "/syzkaller/managers/kvm-direct-sandbox/workdir/gvisor_root" "ci-gvisor-kvm-direct-sandbox-1"
D0316 01:40:08.415871   50562 container.go:592] Signal container "ci-gvisor-kvm-direct-sandbox-1": signal 0
D0316 01:40:08.415912   50562 sandbox.go:814] Signal sandbox "ci-gvisor-kvm-direct-sandbox-1"
D0316 01:40:08.415926   50562 sandbox.go:318] Connecting to sandbox "ci-gvisor-kvm-direct-sandbox-1"
D0316 01:40:08.416120   50562 urpc.go:534] urpc: successfully marshalled 110 bytes.
I0316 01:40:09.786785   50562 debug.go:128] Found sandbox "ci-gvisor-kvm-direct-sandbox-1", PID: 5523
I0316 01:40:09.786847   50562 debug.go:137] Retrieving sandbox stacks
D0316 01:40:09.787629   50562 sandbox.go:932] Stacks sandbox "ci-gvisor-kvm-direct-sandbox-1"
D0316 01:40:09.787667   50562 sandbox.go:318] Connecting to sandbox "ci-gvisor-kvm-direct-sandbox-1"
W0316 01:40:09.787728   50562 error.go:48] FATAL ERROR: retrieving stacks: connecting to control server at PID 5523: connection refused
retrieving stacks: connecting to control server at PID 5523: connection refused
W0316 01:40:09.787877   50562 main.go:338] Failure to execute command, err: 1

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/03/16 01:40 gvisor f693e1334b6f 749688d2 .config console log report ci-gvisor-kvm-direct-sandbox
* Struck through repros no longer work on HEAD.