Hello,
syzbot found the following issue on:
HEAD commit: 99858244924d hdestroy(3): stop freeing key values
git tree: openbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=10e992c6580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link:
https://syzkaller.appspot.com/bug?extid=49593932fc0ac0fcd95d
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/b84e1f2c9fe1/disk-99858244.raw.xz
bsd.gdb:
https://storage.googleapis.com/syzbot-assets/089cfa393044/bsd-99858244.gdb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/f8b686940856/kernel-99858244.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+495939...@syzkaller.appspotmail.com
uvm_fault(0xfffffc806cd0d208, 0x98, 0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff82255678 cs 8 rflags 10246 cr2 98 cpl 0 rsp ffff80002a266040
gsbase 0xffffffff83954ff0 kgsbase 0x0
panic: trap type 6, code=0, pc=ffffffff82255678
Starting stack trace...
panic(ffffffff834f32c3) at panic+0x1d0 sys/kern/subr_prf.c:229
kerntrap(ffff80002a265f90) at kerntra
p+0x30b
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
dovutimens(ffff800045fe8d18,fffffc805f82f048,ffff80002a266150) at dovutimens+0x368 sys/kern/vfs_syscalls.c:2691
sys_futimens(ffff800045fe8d18,ffff80002a2662a0,ffff80002a2661f0) at sys_futimens+0xb3 sys/kern/vfs_syscalls.c:2767
syscall(ffff80002a2662a0) at syscall+0xb17 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80002a2662a0) at syscall+0xb17 sys/arch/amd64/amd64/trap.c:783
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x296c55e6c90, count: 250
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 43b93b83-f320-801a-a1ee-23eab263a335
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 0x000f2600: 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.67
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot>
---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup