lock error in [ 81.ADDR] do_sys_accept

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: 2ce7e4bd PR/54045
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1101884d200000
dashboard link: https://syzkaller.appspot.com/bug?extid=947b0791e49ee9f43407
userspace arch: amd64

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+947b07...@syzkaller.appspotmail.com

[ 81.8659842] panic: lock error: Mutex: mutex_vector_exit,761: assertion
failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffffa9801315cb80
cpu 0 lwp 0xffffa980131825a0
[ 81.8825605] cpu0: Begin traceback...
[ 81.8862919] vpanic() at netbsd:vpanic+0x214
[ 81.8939327] snprintf() at netbsd:snprintf
[ 81.9039545] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
[ 81.9140246] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
[ 81.9256840] do_sys_accept() at netbsd:do_sys_accept+0x346
[ 81.9340066] sys_accept() at netbsd:sys_accept+0xac
[ 81.9443023] sys___syscall() at netbsd:sys___syscall+0xe2
[ 81.9640696] syscall() at netbsd:syscall+0x32e
[ 81.9640696] --- syscall (number 198) ---
[ 81.9750778] 70221603f4aa:
[ 81.9750778] cpu0: End traceback...

[ 81.9750778] dumping to dev 4,1 (offset=0, size=0): not possible
[ 81.9750778] rebooting...
SeaBIOS (version 1.8.2-20190122_225043-google)
Total RAM Size = 0x00000001e0000000 = 7680 MiB
CPUs found: 2 Max CPUs supported: 2
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0
removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f29c0: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Booting from Hard Disk 0...

>> NetBSD/x86 BIOS Boot, Revision 5.10 (Tue Jul 17 14:59:51 UTC 2018) (from
>> NetBSD 8.0)
>> Memory: 639/3144640 k

1. Boot normally
2. Boot single user
3. Disable ACPI
4. Disable ACPI and SMP
5. Drop to boot prompt


---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

[Maxime Villard]

Hopefully that's the last duplicate related to this issue

#syz dup: lock error in do_sys_accept