syzbot


lock error in [ 42.ADDR] do_sys_accept

Status: closed as dup on 2019/05/02 19:10
Reported-by: syzbot+372c77fd23472055b357@syzkaller.appspotmail.com
First crash: 2032d, last: 2032d
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
lock error in [ 81.ADDR] do_sys_accept 1 2082d 2082d

Sample crash report:
[  42.7434863] panic: lock error: Mutex: mutex_vector_exit,761: assertion failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffff918012f07280 cpu 0 lwp 0xffff918012f2c0e0
[  42.7549432] cpu0: Begin traceback...
[  42.7549432] vpanic() at netbsd:vpanic+0x214
[  42.7549432] snprintf() at netbsd:snprintf
[  42.7635425] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
[  42.7735685] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
[  42.7835997] do_sys_accept() at netbsd:do_sys_accept+0x346
[  42.7835997] sys_accept() at netbsd:sys_accept+0xac
[  42.7948258] sys_syscall() at netbsd:sys_syscall+0xe2
[  42.8036551] syscall() at netbsd:syscall+0x348
[  42.8145952] --- syscall (number 0) ---
[  42.8145952] 7a7e04a3f4ca:
[  42.8145952] cpu0: End traceback...

[  42.8261534] dumping to dev 4,1 (offset=0, size=0): not possible
[  42.8261534] rebooting...

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/04/30 11:20 netbsd c0dd5d0fd21b 20f16bef console log report syz C ci2-netbsd
* Struck through repros no longer work on HEAD.