lock error in [ 532.ADDR] do_sys_accept

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: a0aeb9c0 For the rtsock compat code, make sure we create t..
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=17f2f070a00000
dashboard link: https://syzkaller.appspot.com/bug?extid=aa2d446df8190545bfab
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15723d60a00000

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

[ 532.6002654] panic: lock error: Mutex: mutex_vector_exit,761: assertion
failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffffaf8012f2fc40
cpu 0 lwp 0xffffaf8011ff1b40
[ 532.6002654] cpu0: Begin traceback...
[ 532.6002654] vpanic() at netbsd:vpanic+0x214
[ 532.6002654] snprintf() at netbsd:snprintf
[ 532.6002654] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
[ 532.6002654] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
[ 532.6002654] do_sys_accept() at netbsd:do_sys_accept+0x346
[ 532.6002654] sys_paccept() at netbsd:sys_paccept+0x11c
[ 532.6002654] sys___syscall() at netbsd:sys___syscall+0xe2
[ 532.6002654] syscall() at netbsd:syscall+0x348
[ 532.6002654] --- syscall (number 198) ---
[ 532.6002654] 7e701ce3f4aa:
[ 532.6002654] cpu0: End traceback...

[ 532.6002654] dumping to dev 4,1 (offset=0, size=0): not possible
[ 532.6002654] rebooting...
SeaBIOS (version 1.8.2-20190322_093631-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 0x000f29d0: 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#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

[Maxime Villard]

#syz dup: lock error in [ 81.ADDR] do_sys_accept