panic: pmap_enter: PG_PVLIST mapping with unmanaged page: va ADDR, opte ADDR, pa ADDR (2)

0 views
Skip to first unread message

syzbot

unread,
Apr 9, 2024, 11:50:19 AMApr 9
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b226cd0be9f7 regen
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11f81199180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=efe746046e62c8b661ab

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0e7a1709922a/disk-b226cd0b.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/a1c14c0c4b47/bsd-b226cd0b.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d9bd487f4a13/kernel-b226cd0b.xz

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

�panic: pmap_enter: PG_PVLIST mapping with unmanaged page: va 0x1b33a21000, opte 0xffffffffffffffff, pa 0x6779d000
Starting stack trace...
panic(ffffffff828580fa) at panic+0x16f sys/kern/subr_prf.c:229
pmap_enter(fffffd807f002ba0,1b33a21000,6779d000,3,20) at pmap_enter+0xd04
uvm_fault_lower_lookup(ffff80002a213fb0,ffff80002a213fe8,ffff80002a213f30) at uvm_fault_lower_lookup+0x29b sys/uvm/uvm_fault.c:1192
uvm_fault_lower(ffff80002a213fb0,ffff80002a213fe8,ffff80002a213f30,0) at uvm_fault_lower+0x62 sys/uvm/uvm_fault.c:1227
uvm_fault(fffffd80694df370,1b33a20000,0,1) at uvm_fault+0x255 sys/uvm/uvm_fault.c:637
upageflttrap(ffff80002a214130,1b33a20000) at upageflttrap+0x8b sys/arch/amd64/amd64/trap.c:188
usertrap(ffff80002a214130) at usertrap+0x227 sys/arch/amd64/amd64/trap.c:436
recall_trap() at recall_trap+0x8
end of kernel
end trace frame: 0x7718e47e08c0, count: 249
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
Reply all
Reply to author
Forward
0 new messages