Hello,
syzbot found the following issue on:
HEAD commit: 4f401870a326 Rename arguments of X509_STORE_CTX_init()
git tree: openbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=14a589c2280000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link:
https://syzkaller.appspot.com/bug?extid=9dbff2dd55bb885df04c
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/6783467025ed/disk-4f401870.raw.xz
bsd.gdb:
https://storage.googleapis.com/syzbot-assets/45035e4becbf/bsd-4f401870.gdb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/ad6ff3817c4f/kernel-4f401870.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+9dbff2...@syzkaller.appspotmail.com
panic: vpoapn_giecn: ekrice_brnadelop
diSatganortsitnicg asssetratcionk "t!ra_kcee.rn.e.l
_lock_held()" failed: file "/sypanizkc(aflflfeffr/ffmfa8nag2er7s/8m51u0lt5i)c oart e/kernel/sys/kern/kern_pfaonrkic.+0c"x16,f
line 675
Parallel traceback, svupop_pgernesesriecd_.ba..d
op(ffff80002614ae78) at vop_generic_badop+0x1f sys/kern/vfs_default.c:133
VOP_STRATEGY(fffffd8066adf510,fffffd8063cb75b8) at VOP_STRATEGY+0x9f sys/kern/vfs_vops.c:628
bwrite(fffffd8063cb75b8) at bwrite+0x1f4 sys/kern/vfs_bio.c:760
VOP_BWRITE(fffffd8063cb75b8) a
td ump to dev 4,1 not possViObPle_B
WRITE+0x4e
rpaenbioco:tin kegr.n.e.
l diagnostiSeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2 Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 5539092a-1476-82b6-0a34-88b96a0f4c53
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 0x000f2830: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.56
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> trace
---
This report 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 issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup