corrupted report (6)

1 view
Skip to first unread message

syzbot

unread,
Sep 18, 2021, 4:58:23 PM9/18/21
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 71c23e2a74ef Fix subjectAlternativeName (SAN) generation f..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1299f527300000
kernel config: https://syzkaller.appspot.com/x/.config?x=fe55924c11e64b0a
dashboard link: https://syzkaller.appspot.com/bug?extid=ef4f9b71feec24fcb6a7

Unfortunately, I don't have any reproducer for this issue yet.

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

uvm_fault(0xffffffff8281eb00, 0xffff80002116115c, 0, 2) -> d
fatal page fault in supervisor mode
trap type 6 code 2 rip ffffffff814ed2e5 cs 8 rflags 10206 cr2 ffff80002116115c cpl 0 rsp ffff80002168d558
gsbase 0xffffffff827beff0 kgsbase 0x0
panic: trap type 6, code=2, pc=ffffffff814ed2e5
Starting stack trace...
panic(ffffffff82436e9f) at panic+0x155 sys/kern/subr_prf.c:233
kerntrap(ffff80002168d4a0) at kerntrap+0x1b7 sys/arch/amd64/amd64/trap.c:313
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
memset() at memset+0x45
ffs_write(ffff80002168d830) at ffs_write+0x932 sys/ufs/ffs/ffs_vnops.c:403
VOP_WRITE(fffffd806e49f2f0,ffff80002168da50,3,fffffd807f7d8a80) at VOP_WRITE+0xc6 sys/kern/vfs_vops.c:272
vn_write(fffffd80768530f8,ffff80002168da50,0) at vn_write+0x14c sys/kern/vfs_vnops.c:414
dofilewritev(ffff80002165bcf0,e,ffff80002168da50,0,ffff80002168db50) at dofilewritev+0x1a3 sys/kern/sys_generic.c:365
sys_writev(ffff80002165bcf0,ffff80002168daf0,ffff80002168db50) at sys_writev+0xa7 sys/kern/sys_generic.c:312
syscall(ffff80002168dbc0) at syscall+0x571 sys/arch/amd64/amd64/trap.c:587
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7f7ffffede90, count: 246
End of stack trace.

dump to dev 4,1 not possible
rebooting...
SeaBIOS (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 1f5eaa37-9319-de71-8c79-d2e486f4a21c
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 0x000f2430: 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.53
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.
Reply all
Reply to author
Forward
0 new messages