SYZFAIL: repeatedly failed to execute the program

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ba080721f3fe Rewrite bytes/sec calculation using fixed poi..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=154449a5980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=d1318ccd77555c585823

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ab4f23d4e4a8/disk-ba080721.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/d7856e4af6a6/bsd-ba080721.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e4b48808aede/kernel-ba080721.xz

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

SYZFAIL: repeatedly failed to execute the program
proc=4 req=449 state=1 status=127 (errno 4: Interrupted system call)
uvm_fault(0xffffffff83564fe0, 0xffff800019742018, 0, 1) -> d
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff81715c5e cs 8 rflags 10202 cr2 ffff800019742018 cpl 0 rsp ffff800029fe5600
gsbase 0xffff800029b7bff0 kgsbase 0x0
panic: trap type 6, code=0, pc=ffffffff81715c5e
Starting stack trace...
panic(ffffffff82fd1197) at panic+0x1d0 sys/kern/subr_prf.c:229
kerntrap(ffff800029fe5550) at kerntrap+0x29b sys/arch/amd64/amd64/trap.c:327
alltraps_kern_meltdown() at alltraps_kern_meltdown+0x7b
ffs2_balloc(fffffd806c85c890,3f000,1000,fffffd807f7d3e38,1,ffff800029fe57c8) at ffs2_balloc+0x9fe sys/ufs/ffs/ffs_balloc.c:614
ffs_write(ffff800029fe5850) at ffs_write+0x4f9 sys/ufs/ffs/ffs_vnops.c:345
VOP_WRITE(fffffd807aca1e90,ffff800029fe58e8,0,fffffd807f7d3e38) at VOP_WRITE+0x102 sys/kern/vfs_vops.c:245
uvn_io(fffffd806cf74840,ffff800029fe5a80,1,39,1) at uvn_io+0x49c sys/uvm/uvm_vnode.c:1269
uvm_pager_put(fffffd806cf74840,fffffd8008073a20,ffff800029fe5b18,ffff800029fe5b50,39,0,a051df91e2faf6fc) at uvm_pager_put+0x18e sys/uvm/uvm_pager.c:545
uvn_flush(fffffd806cf74840,0,0,19) at uvn_flush+0x72a sys/uvm/uvm_vnode.c:725
uvn_detach(fffffd806cf74840) at uvn_detach+0xb8 sys/uvm/uvm_vnode.c:360
uvm_unmap_detach(ffff800029fe5c60,1) at uvm_unmap_detach+0x26b sys/uvm/uvm_map.c:1380
uvm_map_teardown(fffffd80092eea50) at uvm_map_teardown+0x3f7 sys/uvm/uvm_map.c:2540
uvmspace_free(fffffd80092eea50) at uvmspace_free+0xe8 sys/uvm/uvm_map.c:3447
reaper(ffff800029fd8a28) at reaper+0x25b sys/kern/kern_exit.c:480
end trace frame: 0x0, count: 243
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 50375c3b-e826-8a7e-06ca-b163c863336b
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 0x000f27c0: 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> 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 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