lock error in [ 694.ADDR] do_sys_accept

[syzbot]

Hello,

syzbot found the following crash on:

HEAD commit: d4323b20 Split the description for EINVAL into two pieces,..
git tree: netbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=169af09f200000
dashboard link: https://syzkaller.appspot.com/bug?extid=dd422d1b83a40a8818b7

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

[ 694.6288385] panic: lock error: Mutex: mutex_vector_exit,761: assertion
failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffffdd8012f195c0
cpu 0 lwp 0xffffdd80130269e0
[ 694.6498741] cpu0: Begin traceback...
[ 694.6561897] vpanic() at netbsd:vpanic+0x214
[ 694.6699227] snprintf() at netbsd:snprintf
[ 694.6836718] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
[ 694.6975986] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
[ 694.7126312] do_sys_accept() at netbsd:do_sys_accept+0x346
[ 694.7249073] sys_paccept() at netbsd:sys_paccept+0x11c
[ 694.7388065] sys___syscall() at netbsd:sys___syscall+0xe2
[ 694.7525830] syscall() at netbsd:syscall+0x32e
[ 694.7684322] --- syscall (number 198) ---
[ 694.7798506] 7d6905c3f4aa:
[ 694.7798506] cpu0: End traceback...

[ 694.7798506] dumping to dev 4,1 (offset=0, size=0): not possible
[ 694.7798506] 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 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 08/04/2019 à 16:28, syzbot a écrit :
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:    d4323b20 Split the description for EINVAL into two pieces,..
> git tree:       netbsd
> console output: https://syzkaller.appspot.com/x/log.txt?x=169af09f200000
> dashboard link: https://syzkaller.appspot.com/bug?extid=dd422d1b83a40a8818b7
>
> 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+dd422d...@syzkaller.appspotmail.com
>
> [ 694.6288385] panic: lock error: Mutex: mutex_vector_exit,761: assertion failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffffdd8012f195c0 cpu 0 lwp 0xffffdd80130269e0
> [ 694.6498741] cpu0: Begin traceback...
> [ 694.6561897] vpanic() at netbsd:vpanic+0x214
> [ 694.6699227] snprintf() at netbsd:snprintf
> [ 694.6836718] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
> [ 694.6975986] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
> [ 694.7126312] do_sys_accept() at netbsd:do_sys_accept+0x346
> [ 694.7249073] sys_paccept() at netbsd:sys_paccept+0x11c
> [ 694.7388065] sys___syscall() at netbsd:sys___syscall+0xe2
> [ 694.7525830] syscall() at netbsd:syscall+0x32e
> [ 694.7684322] --- syscall (number 198) ---
> [ 694.7798506] 7d6905c3f4aa:
> [ 694.7798506] cpu0: End traceback...

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