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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bcc953340d3a Appease mandoc -Tlint
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=15d1bf9f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=1df602a3fe62e352703d

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7caa39978512/disk-bcc95334.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/37ac815c63e0/bsd-bcc95334.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d068202fe3a3/kernel-bcc95334.xz

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

panic: Non dma-reachable buffer at curaddr 0xffff80002a45cad0(raw)
Starting stack trace...
panic(ffffffff830810e1) at panic+0x1ba sys/kern/subr_prf.c:229
_bus_dmamap_load_buffer(ffff80002a45cb58,ffff800000180000,ffff80001a7e2000,1800,0,ffff80002a45cb50,d36a2e16567bb62a,1800,ffff800000180000,ffff80001a7e2000) at _bus_dmamap_load_buffer+0x5ff sys/arch/amd64/amd64/bus_dma.c:727
_bus_dmamap_load(ffffffff83436de8,ffff800000180000,ffff80001a7e2000,1800,0,401) at _bus_dmamap_load+0xc2 sys/arch/amd64/amd64/bus_dma.c:271
vioscsi_scsi_cmd(fffffd806a1dc7a8) at vioscsi_scsi_cmd+0x221 sys/dev/pv/vioscsi.c:220

sdstart(fffffd806a1dc7a8) at sdstart+0x4b2 sys/scsi/sd.c:709
scsi_iopool_run(ffff8000000a2048) at scsi_iopool_run+0x165 sys/scsi/scsi_base.c:423
scsi_xsh_runqueue(ffff80000002f800) at scsi_xsh_runqueue+0x39d sys/scsi/scsi_base.c:599
scsi_xsh_add(ffff800000024b80) at scsi_xsh_add+0x115 sys/scsi/scsi_base.c:538
sdstrategy(fffffd80642a1580) at sdstrategy+0x21b sys/scsi/sd.c:567
spec_strategy(ffff80002a45ce18) at spec_strategy+0x45 sys/kern/spec_vnops.c:448
VOP_STRATEGY(fffffd807eb51000,fffffd80642a1580) at VOP_STRATEGY+0xcc sys/kern/vfs_vops.c:634
ufs_strategy(ffff80002a45cec8) at ufs_strategy+0x1f6
VOP_STRATEGY(fffffd8067fa4048,fffffd80642a1580) at VOP_STRATEGY+0xcc sys/kern/vfs_vops.c:634
bwrite(fffffd80642a1580) at bwrite+0x28a sys/kern/vfs_bio.c:757
VOP_BWRITE(fffffd80642a1580) at VOP_BWRITE+0x60 sys/kern/vfs_vops.c:646
buf_daemon(ffff80002a457958) at buf_daemon+0x3b9
end trace frame: 0x0, count: 241
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.

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

[syzbot]

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