lock error in [ 1862.ADDR] do_sys_accept

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: a5a5ed5a correct debug message, d->myport has network byte..
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=169404ab200000
dashboard link: https://syzkaller.appspot.com/bug?extid=bdcb1d564a060c3d74d0

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+bdcb1d...@syzkaller.appspotmail.com

[ 1862.5384632] panic: lock error: Mutex: mutex_vector_exit,761: assertion
failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffffa60012f86680
cpu 0 lwp 0xffffa60012fdc540
[ 1862.5557202] cpu0: Begin traceback...
[ 1862.5599599] vpanic() at netbsd:vpanic+0x214
[ 1862.5715820] snprintf() at netbsd:snprintf
[ 1862.5821638] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
[ 1862.5933029] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
[ 1862.6058315] do_sys_accept() at netbsd:do_sys_accept+0x346
[ 1862.6155387] sys_accept() at netbsd:sys_accept+0xac
[ 1862.6266643] sys___syscall() at netbsd:sys___syscall+0xe2
[ 1862.6377921] syscall() at netbsd:syscall+0x32e
[ 1862.6496122] --- syscall (number 198) ---
[ 1862.6600408] 7ce76943f4aa:
[ 1862.6600408] cpu0: End traceback...

[ 1862.6600408] dumping to dev 4,1 (offset=0, size=0): not possible
[ 1862.6600408] 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#status for how to communicate with syzbot.

[Maxime Villard]

Le 01/04/2019 à 03:14, syzbot a écrit :
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:    a5a5ed5a correct debug message, d->myport has network byte..
> git tree:       netbsd
> console output: https://syzkaller.appspot.com/x/log.txt?x=169404ab200000
> dashboard link: https://syzkaller.appspot.com/bug?extid=bdcb1d564a060c3d74d0
>
> 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+bdcb1d...@syzkaller.appspotmail.com
>
> [ 1862.5384632] panic: lock error: Mutex: mutex_vector_exit,761: assertion failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffffa60012f86680 cpu 0 lwp 0xffffa60012fdc540
> [ 1862.5557202] cpu0: Begin traceback...
> [ 1862.5599599] vpanic() at netbsd:vpanic+0x214
> [ 1862.5715820] snprintf() at netbsd:snprintf
> [ 1862.5821638] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
> [ 1862.5933029] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
> [ 1862.6058315] do_sys_accept() at netbsd:do_sys_accept+0x346
> [ 1862.6155387] sys_accept() at netbsd:sys_accept+0xac
> [ 1862.6266643] sys___syscall() at netbsd:sys___syscall+0xe2
> [ 1862.6377921] syscall() at netbsd:syscall+0x32e
> [ 1862.6496122] --- syscall (number 198) ---
> [ 1862.6600408] 7ce76943f4aa:
> [ 1862.6600408] cpu0: End traceback...

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