syzbot


panic: Sentry detected 14 stuck task(s):

Status: closed as dup on 2020/09/13 08:11
Reported-by: syzbot+de71234a7a6075768955@syzkaller.appspotmail.com
First crash: 1532d, last: 1506d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
panic: Sentry detected stuck tasks C 506 1464d 1485d

Sample crash report:
panic: Sentry detected 14 stuck task(s):
	Task tid: 11 (0xb), entered RunSys state 3m38.36s ago.
	Task tid: 13585 (0x3511), entered RunSys state 3m38.69s ago.
	Task tid: 10627 (0x2983), entered RunSys state 3m10.48s ago.
	Task tid: 2 (0x2), entered RunSys state 3m10.48s ago.
	Task tid: 13582 (0x350e), entered RunSys state 3m37.95s ago.
	Task tid: 9 (0x9), entered RunSys state 3m10.48s ago.
	Task tid: 32 (0x20), entered RunSys state 3m34.23s ago.
	Task tid: 13584 (0x3510), entered RunSys state 3m38.7s ago.
	Task tid: 13586 (0x3512), entered RunSys state 3m38.7s ago.
	Task tid: 39 (0x27), entered RunSys state 3m37.14s ago.
	Task tid: 6443 (0x192b), entered RunSys state 3m10.48s ago.
	Task tid: 13581 (0x350d), entered RunSys state 3m38.69s ago.
	Task tid: 31 (0x1f), entered RunSys state 3m38.36s ago.
	Task tid: 13583 (0x350f), entered RunSys state 3m38.7s 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.

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/08/22 14:36 gvisor 69008b68b0a7 6436ce4b .config console log report ci-gvisor-ptrace-proxy-sandbox-race
2020/07/27 16:25 gvisor 2ecf66903ed3 cb93dc6a .config console log report ci-gvisor-kvm-proxy-overlay-sandbox
* Struck through repros no longer work on HEAD.