syzbot


panic: Sentry detected 13 stuck task(s):

Status: auto-closed as invalid on 2020/08/22 01:22
Reported-by: syzbot+43a7ae6cc13ee210647f@syzkaller.appspotmail.com
First crash: 1647d, last: 1647d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor panic: Sentry detected 13 stuck task(s): (2) 7 1537d 1535d 0/26 closed as dup on 2020/09/13 08:10

Sample crash report:
panic: Sentry detected 13 stuck task(s):
	Task tid: 65 (0x41), entered RunSys state 3m17.82s ago.
	Task tid: 90 (0x5a), entered RunSys state 3m25.71s ago.
	Task tid: 28860 (0x70bc), entered RunSys state 3m28.85s ago.
	Task tid: 89 (0x59), entered RunSys state 3m25.68s ago.
	Task tid: 28856 (0x70b8), entered RunSys state 3m28.82s ago.
	Task tid: 28861 (0x70bd), entered RunSys state 3m28.05s ago.
	Task tid: 28859 (0x70bb), entered RunSys state 3m28.85s ago.
	Task tid: 28851 (0x70b3), entered RunSys state 3m28.85s ago.
	Task tid: 28848 (0x70b0), entered RunSys state 3m28.81s ago.
	Task tid: 91 (0x5b), entered RunSys state 3m25.66s ago.
	Task tid: 28857 (0x70b9), entered RunSys state 3m28.85s ago.
	Task tid: 87 (0x57), entered RunSys state 3m25.66s ago.
	Task tid: 28858 (0x70ba), entered RunSys state 3m28.86s 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 (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/05/24 01:21 gvisor ba2bf9fc13c2 96c92ad3 .config console log report ci-gvisor-ptrace-direct-overlay-host-race
* Struck through repros no longer work on HEAD.