Hello,
syzbot found the following crash on:
HEAD commit: 0710e7fb Avoid marking up semicolons.
git tree: netbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=119984d3200000
dashboard link:
https://syzkaller.appspot.com/bug?extid=a588f69bf06c7da1aafa
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+a588f6...@syzkaller.appspotmail.com
[ 919.7135300] panic: lock error: Mutex: mutex_vector_exit,761: assertion
failed: MUTEX_OWNER(mtx->mtx_owner) == curthread: lock 0xffffdc0013092b40
cpu 1 lwp 0xffffdc001307ea60
[ 919.7346621] cpu1: Begin traceback...
[ 919.7452282] vpanic() at netbsd:vpanic+0x214
[ 919.7557943] snprintf() at netbsd:snprintf
[ 919.7663588] lockdebug_abort() at netbsd:lockdebug_abort+0x14c
[ 919.7769236] mutex_vector_exit() at netbsd:mutex_vector_exit+0x1bc
[ 919.7874912] do_sys_accept() at netbsd:do_sys_accept+0x346
[ 919.7980551] sys_accept() at netbsd:sys_accept+0xac
[ 919.8086207] sys___syscall() at netbsd:sys___syscall+0xe2
[ 919.8297540] syscall() at netbsd:syscall+0x32e
[ 919.8297540] --- syscall (number 198) ---
[
919.8403176] 76a0c083f4aa:
[ 919.8403176] cpu1: End traceback...
[ 919.8403176] dumping to dev 4,1 (offset=0, size=0): not possible
[ 919.8508832] 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.