panic: uvm_fault_unwire_locked: adWdArReNssI NnG:o tSP iLn maNpO

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 80ba1745ccfd make_addressRange: unused bits in max must be..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1129e9ba580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=5983eb4dd2fb9674f794

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ec8a742bd6e3/disk-80ba1745.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/10155d40d728/bsd-80ba1745.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/781833d9c9f5/kernel-80ba1745.xz

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

panic: uvm_fault_unwire_locked: adWdArReNssI NnG:o tSP iLn maNpO
T StLoOWERpEpeD dO Nat SYSCALL 73 487424 EXIT 0 a
db_enter+0x25: addq $0x8,%rsp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*268011 64242 0 0 0x4000000 0K syz-executor
487091 64242 0 0 0x4000000 1 syz-executor
db_enter() at db_enter+0x25 sys/arch/amd64/amd64/db_interface.c:438
panic(ffffffff8349b99e) at panic+0x1e5 sys/kern/subr_prf.c:198
uvm_fault_unwire_locked(fffffd806b0a49a8,2000003d0000,2000003d7000) at uvm_fault_unwire_locked+0x4be
uvm_fault_wire(fffffd806b0a49a8,2000003d0000,2000003e1000,1) at uvm_fault_wire+0x12d uvm_fault_unwire sys/uvm/uvm_fault.c:1724 [inline]
uvm_fault_wire(fffffd806b0a49a8,2000003d0000,2000003e1000,1) at uvm_fault_wire+0x12d sys/uvm/uvm_fault.c:1706
uvm_vslock_device(ffff8000333a8d18,2000003d04c0,10000,1,ffff800030fa7108) at uvm_vslock_device+0x112 sys/uvm/uvm_glue.c:169
physio(ffffffff81d5b4c0,d02,0,ffffffff81d5bd10,ffff800030fa73e8) at physio+0x257 sys/kern/kern_physio.c:139
spec_write(ffff800030fa7230) at spec_write+0x11f sys/kern/spec_vnops.c:302
VOP_WRITE(fffffd805db19ea8,ffff800030fa73e8,5,fffffd80097fd3a8) at VOP_WRITE+0x101 sys/kern/vfs_vops.c:245
vn_write(fffffd80601139d8,ffff800030fa73e8,0) at vn_write+0x1d3 sys/kern/vfs_vnops.c:414
dofilewritev(ffff8000333a8d18,8,ffff800030fa73e8,0,ffff800030fa74a0) at dofilewritev+0x2bd sys/kern/sys_generic.c:384
sys_write(ffff8000333a8d18,ffff800030fa7550,ffff800030fa74a0) at sys_write+0xa2 sys/kern/sys_generic.c:300
syscall(ffff800030fa7550) at syscall+0xbd4 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff800030fa7550) at syscall+0xbd4 sys/arch/amd64/amd64/trap.c:783
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xf5f776982a0, count: 2
https://www.openbsd.org/ddb.html describes the minimum info required in bug
reports. Insufficient info makes it difficult to find and fix bugs.


---
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