panic: uvm_fault_unwir

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8d6481d63f8c ec.h: remove last SunPro pragmas
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=15bd1478580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=2be3413f15c2a997d434

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/35098d94ecb3/disk-8d6481d6.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/84374f303f8d/bsd-8d6481d6.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7f2ff24f3392/kernel-8d6481d6.xz

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

panic: uvm_fault_unwir
e_locked: address not i
n map
Starting stack trace...
panic(ffffffff833ddcb0) at panic+0x1ba sys/kern/subr_prf.c:229
uvm_fault_unwire_locked(fffffd806c0ae9e8,400000000000,400000001000) at uvm_fault_unwire_locked+0x487 sys/uvm/uvm_fault.c:1741
uvm_fault_unwire(fffffd806c0ae9e8,400000000000,400000001000) at uvm_fault_unwire+0x55 sys/uvm/uvm_fault.c:1704
kern_sysctl_dirs(4e,ffff80003ca273a8,1,400000000100,ffff80003ca273d8,0,c46d562a049c8d54,1) at kern_sysctl_dirs+0x5d1
kern_sysctl(ffff80003ca273a4,2,400000000100,ffff80003ca273d8,0,27,f928eb32f97a0451) at kern_sysctl+0x12d sys/kern/kern_sysctl.c:526
sys_sysctl(ffff80003ad4b4b8,ffff80003ca27510,ffff80003ca27460) at sys_sysctl+0x425

syscall(ffff80003ca27510) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x26fbcd7c430, count: 249
End of stack trace.
syncing disks...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.