assert "pmap->pm_type != PMAP_TYPE_EPT" failed in pmap.c (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 55906bae5af5 As of the documentation, the UTP Command Desc..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11835520980000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=116f728e8f2fd3210d63

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f9f05cc9952c/disk-55906bae.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/58060a0130bb/bsd-55906bae.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b7f760358197/kernel-55906bae.xz

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

login: panic: kernel diagnostic assertion "pmap->pm_type != PMAP_TYPE_EPT" failed: file "/syzkaller/managers/multicore/kernel/sys/arch/amd64/amd64/pmap.c", line 412
Starting stack trace...
panic(ffffffff82958834) at panic+0x16f sys/kern/subr_prf.c:229
__assert(ffffffff8290dd82,ffffffff8293782d,19c,ffffffff829402f6) at __assert+0x29 sys/kern/subr_prf.c:157
pmap_page_remove(fffffd80084ff680) at pmap_page_remove+0x5a4 pmap_map_ptes sys/arch/amd64/amd64/pmap.c:426 [inline]
pmap_page_remove(fffffd80084ff680) at pmap_page_remove+0x5a4 sys/arch/amd64/amd64/pmap.c:1950
uvm_anfree_list(fffffd80596f3618,0) at uvm_anfree_list+0x98
amap_wipeout(fffffd8069554598) at amap_wipeout+0x1af sys/uvm/uvm_amap.c:502
uvm_unmap_detach(ffff80002a155680,1) at uvm_unmap_detach+0x7d sys/uvm/uvm_map.c:1354
uvm_map_teardown(fffffd806b5748b0) at uvm_map_teardown+0x2f8 sys/uvm/uvm_map.c:2554
uvmspace_free(fffffd806b5748b0) at uvmspace_free+0xa6 sys/uvm/uvm_map.c:3461
reaper(ffff80002a1491f8) at reaper+0x197 sys/kern/kern_exit.c:463
end trace frame: 0x0, count: 248
End of stack 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