syzbot


panic: Sentry detected 16 stuck task(s):

Status: closed as dup on 2020/09/13 08:10
Reported-by: syzbot+39f33e13c8d7e01d5be0@syzkaller.appspotmail.com
First crash: 1495d, 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 16 stuck task(s):
	Task tid: 8597 (0x2195), entered RunSys state 3m40.42s ago.
	Task tid: 3 (0x3), entered RunSys state 3m27.69s ago.
	Task tid: 12 (0xc), entered RunSys state 3m27.68s ago.
	Task tid: 7 (0x7), entered RunSys state 3m27.69s ago.
	Task tid: 10 (0xa), entered RunSys state 3m27.69s ago.
	Task tid: 8600 (0x2198), entered RunSys state 3m27.69s ago.
	Task tid: 8 (0x8), entered RunSys state 3m27.68s ago.
	Task tid: 2 (0x2), entered RunSys state 3m27.69s ago.
	Task tid: 5 (0x5), entered RunSys state 3m27.68s ago.
	Task tid: 11 (0xb), entered RunSys state 3m27.69s ago.
	Task tid: 58 (0x3a), entered RunSys state 3m40.44s ago.
	Task tid: 8599 (0x2197), entered RunSys state 3m40.48s ago.
	Task tid: 8594 (0x2192), entered RunSys state 3m40.47s ago.
	Task tid: 4 (0x4), entered RunSys state 3m27.68s ago.
	Task tid: 6 (0x6), entered RunSys state 3m27.69s ago.
	Task tid: 9 (0x9), entered RunSys state 3m27.69s 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/09/08 23:07 gvisor d84ec6c42bd7 abf9ba4f .config console log report ci-gvisor-main
2020/09/02 20:21 gvisor 563f28b7d56c abf9ba4f .config console log report ci-gvisor-ptrace-proxy-sandbox-race
* Struck through repros no longer work on HEAD.