syzbot


panic: Sentry detected 15 stuck task(s):

Status: closed as dup on 2020/09/13 08:10
Reported-by: syzbot+502332b989aeab4f5e93@syzkaller.appspotmail.com
First crash: 1492d, last: 1489d
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 15 stuck task(s):
	Task tid: 32 (0x20), entered RunSys state 3m43.9s ago.
	Task tid: 3399 (0xd47), entered RunSys state 3m44.87s ago.
	Task tid: 3401 (0xd49), entered RunSys state 3m44.9s ago.
	Task tid: 3396 (0xd44), entered RunSys state 3m44.12s ago.
	Task tid: 3402 (0xd4a), entered RunSys state 3m44.9s ago.
	Task tid: 6 (0x6), entered RunSys state 3m44.85s ago.
	Task tid: 8 (0x8), entered RunSys state 3m44.08s ago.
	Task tid: 3398 (0xd46), entered RunSys state 3m44.85s ago.
	Task tid: 36 (0x24), entered RunSys state 3m43.9s ago.
	Task tid: 2 (0x2), entered RunSys state 3m44.85s ago.
	Task tid: 3400 (0xd48), entered RunSys state 3m44.9s ago.
	Task tid: 31 (0x1f), entered RunSys state 3m43.9s ago.
	Task tid: 19 (0x13), entered RunSys state 3m41.06s ago.
	Task tid: 13 (0xd), entered RunSys state 3m43.9s ago.
	Task tid: 5 (0x5), entered RunSys state 3m44.85s 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 (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/09/08 15:37 gvisor fada564c83b3 abf9ba4f .config console log report ci-gvisor-ptrace-direct-overlay-host-race
2020/09/08 13:16 gvisor fada564c83b3 abf9ba4f .config console log report ci-gvisor-main
2020/09/05 19:13 gvisor 2202812e074a abf9ba4f .config console log report ci-gvisor-ptrace-proxy-sandbox-race
* Struck through repros no longer work on HEAD.