panic: Non dma-reachable buffer at curaddr ADDR(raw)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1e5b016c5082 sync for __syscall removal
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=12ea7635c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=6a460c46781090bf0e39

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/452af0b271ef/disk-1e5b016c.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/5145fa4f4c7c/bsd-1e5b016c.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/992507fc6105/kernel-1e5b016c.xz

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

panic: Non dma-reachable buffer at curaddr 0xffff8000216afaf0(raw)
Starting stack trace...
panic(ffffffff82788c01) at panic+0x155 sys/kern/subr_prf.c:229
_bus_dmamap_load_buffer(ffff8000216afb80,ffff800000191000,ffff80000b34f000,4000,0,401,47a0466bdde129cf,4000,ffff800000191000) at _bus_dmamap_load_buffer+0x386 sys/arch/amd64/amd64/bus_dma.c:589
_bus_dmamap_load(ffffffff82ae51d0,ffff800000191000,ffff80000b34f000,4000,0,401) at _bus_dmamap_load+0x97 sys/arch/amd64/amd64/bus_dma.c:179
vioscsi_scsi_cmd(fffffd80715882a0) at vioscsi_scsi_cmd+0x1ac sys/dev/pv/vioscsi.c:219
sdstart(fffffd80715882a0) at sdstart+0x40a sys/scsi/sd.c:709

scsi_iopool_run(ffff8000000a2048) at scsi_iopool_run+0x10a scsi_ioh_pending sys/scsi/scsi_base.c:405 [inline]
scsi_iopool_run(ffff8000000a2048) at scsi_iopool_run+0x10a sys/scsi/scsi_base.c:421
scsi_xsh_runqueue(ffff80000002f800) at scsi_xsh_runqueue+0x203 sys/scsi/scsi_base.c:598
scsi_xsh_add(ffff800000024b80) at scsi_xsh_add+0xc9 sys/scsi/scsi_base.c:536
sdstrategy(fffffd807b443ea0) at sdstrategy+0x187 sys/scsi/sd.c:567
spec_strategy(ffff8000216afe48) at spec_strategy+0x75 sys/kern/spec_vnops.c:451
VOP_STRATEGY(fffffd807efcf438,fffffd807b443ea0) at VOP_STRATEGY+0x9b sys/kern/vfs_vops.c:628
ufs_strategy(ffff8000216afef8) at ufs_strategy+0x15a
VOP_STRATEGY(fffffd807c633638,fffffd807b443ea0) at VOP_STRATEGY+0x9b sys/kern/vfs_vops.c:628
bwrite(fffffd807b443ea0) at bwrite+0x1e7 sys/kern/vfs_bio.c:760
VOP_BWRITE(fffffd807b443ea0) at VOP_BWRITE+0x4a sys/kern/vfs_vops.c:640
ffs_write(ffff8000216b00c0) at ffs_write+0x6fe sys/ufs/ffs/ffs_vnops.c:380
VOP_WRITE(fffffd807c633638,ffff8000216b0170,3,fffffd807f7d76e8) at VOP_WRITE+0xbf sys/kern/vfs_vops.c:245
ktrwriteraw(ffff8000ffff8830,fffffd807c633638,fffffd807f7d76e8,ffff8000216b0230,ffff8000216b0210) at ktrwriteraw+0x146 sys/kern/kern_ktrace.c:661
ktrsysret(ffff8000ffff8830,30,0,ffff8000216b0330) at ktrsysret+0x158 ktrwrite2 sys/kern/kern_ktrace.c:624 [inline]
ktrsysret(ffff8000ffff8830,30,0,ffff8000216b0330) at ktrsysret+0x158 sys/kern/kern_ktrace.c:206
syscall(ffff8000216b03b0) at syscall+0x5a7 mi_syscall_return sys/sys/syscall_mi.h:139 [inline]
syscall(ffff8000216b03b0) at syscall+0x5a7 sys/arch/amd64/amd64/trap.c:646
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7f7ffffeb610, count: 236
End of stack trace.
set $lines = 0
set $maxwidth = 0
show panic
trace
show registers
show proc
ps
show all locks
show malloc
show all pools
machine ddbcpu 0
trace
machine ddbcpu 1
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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.