Hello,
syzbot found the following issue on:
HEAD commit: 56163c0cd41e consistently use one directory term
git tree: openbsd
console output:
https://syzkaller.appspot.com/x/log.txt?x=128bb532580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link:
https://syzkaller.appspot.com/bug?extid=793fee8c3c8257999cae
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/d54da3a254eb/disk-56163c0c.raw.xz
bsd.gdb:
https://storage.googleapis.com/syzbot-assets/6f4ed462ed6c/bsd-56163c0c.gdb.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/01d7cd5e429d/kernel-56163c0c.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+793fee...@syzkaller.appspotmail.com
panic: pmap_remove_ptes: managed page without PG_PVLIST: va 0x1b2d44a000, opte 0x6bbb4001
Starting stack trace...
panic(ffffffff833c8e48) at panic+0x1d0 sys/kern/subr_prf.c:229
pmap_remove_pte(fffffd800b062200,fffffd8008899640,7f800d96a100,1b2d420000,1b2d600000,0) at pmap_remove_pte
pmap_do_remove(fffffd800b062200,1b2d420000,1b2d820000,0) at pmap_do_remove+0x589 sys/arch/amd64/amd64/pmap.c:1920
uvm_unmap_kill_entry_withlock(fffffd806ca8f018,fffffd806cb48de8,0) at uvm_unmap_kill_entry_withlock+0x269 sys/uvm/uvm_map.c:1863
uvm_map_teardown(fffffd806ca8f018) at uvm_map_teardown+0x117 uvm_map_addr_RBT_LEFT sys/uvm/uvm_map.h:-1 [inline]
uvm_map_teardown(fffffd806ca8f018) at uvm_map_teardown+0x117 sys/uvm/uvm_map.c:2486
exit1(ffff8000fffeba10,0,0,1) at exit1+0x6fc sys/kern/kern_exit.c:260
sys_exit(ffff8000fffeba10,ffff80003a405ee0,ffff80003a405e30) at sys_exit+0x1a sys/kern/kern_exit.c:-1
syscall(ffff80003a405ee0) at syscall+0xb17 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003a405ee0) at syscall+0xb17 sys/arch/amd64/amd64/trap.c:765
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7265fc72fb90, 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