syzbot


panic: Sentry detected 17 stuck task(s):

Status: closed as dup on 2020/09/13 08:11
Reported-by: syzbot+9dec4a8e30e9b2ecacc6@syzkaller.appspotmail.com
First crash: 1540d, last: 1492d
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 17 stuck task(s):
	Task tid: 2 (0x2), entered RunSys state 3m33.74s ago.
	Task tid: 7 (0x7), entered RunSys state 3m33.73s ago.
	Task tid: 10 (0xa), entered RunSys state 3m33.74s ago.
	Task tid: 5 (0x5), entered RunSys state 3m33.74s ago.
	Task tid: 11 (0xb), entered RunSys state 3m33.72s ago.
	Task tid: 14 (0xe), entered RunSys state 3m33.74s ago.
	Task tid: 18 (0x12), entered RunSys state 3m33.73s ago.
	Task tid: 20 (0x14), entered RunSys state 3m33.74s ago.
	Task tid: 16 (0x10), entered RunSys state 3m33.74s ago.
	Task tid: 8 (0x8), entered RunSys state 3m33.72s ago.
	Task tid: 6 (0x6), entered RunSys state 3m33.67s ago.
	Task tid: 15 (0xf), entered RunSys state 3m33.7s ago.
	Task tid: 21 (0x15), entered RunSys state 3m33.74s ago.
	Task tid: 13 (0xd), entered RunSys state 3m33.73s ago.
	Task tid: 3 (0x3), entered RunSys state 3m33.74s ago.
	Task tid: 4 (0x4), entered RunSys state 3m33.74s ago.
	Task tid: 23 (0x17), entered RunSys state 3m33.74s 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/07/19 21:12 gvisor e6894cb99fe4 9c812472 .config console log report syz ci-gvisor-kvm-proxy-overlay-sandbox
2020/09/06 02:45 gvisor 2202812e074a abf9ba4f .config console log report ci-gvisor-main
* Struck through repros no longer work on HEAD.