panic: pool_do_get: pvpl: page empty

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 561bf2d2294a Do not include log.h here since this file is ..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=131ccf4a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=3989e93b588f0307907f

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3bf2430f4ba8/disk-561bf2d2.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/aa7b605a7462/bsd-561bf2d2.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7270ad82e370/kernel-561bf2d2.xz

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

panic: pool_do_get: pvpl: page empty
Starting stack trace...
panic(ffffffff833bd728) at panic+0x1ba sys/kern/subr_prf.c:229
pool_do_get(ffffffff83a51800,2,ffff800035ce98c8) at pool_do_get+0x537 sys/kern/subr_pool.c:732
pool_get(ffffffff83a51800,2) at pool_get+0x11a sys/kern/subr_pool.c:-1
pmap_enter(fffffd806d1d1d88,269b1f17000,74032000,4,24) at pmap_enter+0x1dd sys/arch/amd64/amd64/pmap.c:-1
uvm_fault_lower(ffff800035ce9bf0,ffff800035ce9c28,ffff800035ce9b70) at uvm_fault_lower+0x7a6 sys/uvm/uvm_fault.c:1504
uvm_fault(fffffd806d25da28,269b1f17000,0,4) at uvm_fault+0x241 sys/uvm/uvm_fault.c:-1
upageflttrap(ffff800035ce9d90,269b1f17000) at upageflttrap+0xa0 sys/arch/amd64/amd64/trap.c:192
usertrap(ffff800035ce9d90) at usertrap+0x413 sys/arch/amd64/amd64/trap.c:640
recall_trap() at recall_trap+0x8
end of kernel
end trace frame: 0x766db7c1b6e0, count: 248
End of stack trace.

syncing disks...panic: pool_do_get: pvpl: page empty
Starting stack trace...
panic(ffffffff833bd728) at panic+0x1ba sys/kern/subr_prf.c:229
pool_do_get(ffffffff83a51800,2,ffff800035ce9098) at pool_do_get+0x537 sys/kern/subr_pool.c:732
pool_get(ffffffff83a51800,2) at pool_get+0x11a sys/kern/subr_pool.c:-1
pmap_enter(ffffffff83a514f0,ffff800011046000,6ce7f000,1,31) at pmap_enter+0x1dd sys/arch/amd64/amd64/pmap.c:-1
uvm_pagermapin(ffff800035ce9480,2,0) at uvm_pagermapin+0x1ae sys/uvm/uvm_pager.c:266
uvn_io(fffffd80741460a8,ffff800035ce9480,2,31,1) at uvn_io+0x1d7 sys/uvm/uvm_vnode.c:1167
uvn_put(fffffd80741460a8,ffff800035ce9480,2,31) at uvn_put+0x125 sys/uvm/uvm_vnode.c:891
uvm_pager_put(fffffd80741460a8,fffffd800725cf80,ffff800035ce9520,ffff800035ce9544,31,0,f09798da1e34b2d8) at uvm_pager_put+0x10a sys/uvm/uvm_pager.c:505
uvn_flush(fffffd80741460a8,0,0,31) at uvn_flush+0x68d sys/uvm/uvm_vnode.c:705
uvm_vnp_sync(ffff800000c68400) at uvm_vnp_sync+0x1e7 sys/uvm/uvm_vnode.c:1501
sys_sync(ffff80003c974028,0,0) at sys_sync+0xd4 sys/kern/vfs_syscalls.c:534
vfs_syncwait(ffff80003c974028,1) at vfs_syncwait+0x44 sys/kern/vfs_subr.c:-1
vfs_shutdown(ffff80003c974028) at vfs_shutdown+0x97 sys/kern/vfs_subr.c:1803
boot(100) at boot+0x166 sys/arch/amd64/amd64/machdep.c:929
reboot(100) at reboot+0xa8
panic(ffffffff833bd728) at panic+0x1e3
pool_do_get(ffffffff83a51800,2,ffff800035ce98c8) at pool_do_get+0x537 sys/kern/subr_pool.c:732
pool_get(ffffffff83a51800,2) at pool_get+0x11a sys/kern/subr_pool.c:-1
pmap_enter(fffffd806d1d1d88,269b1f17000,74032000,4,24) at pmap_enter+0x1dd sys/arch/amd64/amd64/pmap.c:-1
uvm_fault_lower(ffff800035ce9bf0,ffff800035ce9c28,ffff800035ce9b70) at uvm_fault_lower+0x7a6 sys/uvm/uvm_fault.c:1504
uvm_fault(fffffd806d25da28,269b1f17000,0,4) at uvm_fault+0x241 sys/uvm/uvm_fault.c:-1
upageflttrap(ffff800035ce9d90,269b1f17000) at upageflttrap+0xa0 sys/arch/amd64/amd64/trap.c:192
usertrap(ffff800035ce9d90) at usertrap+0x413 sys/arch/amd64/amd64/trap.c:640
recall_trap() at recall_trap+0x8
end of kernel
end trace frame: 0x766db7c1b6e0, count: 233
End of stack trace.

dump to dev 4,1 not possible
rebooting...
SeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2 Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 9c8ab089-5fb3-144b-a4ba-2e178800b25c
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f26c0: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.67
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> 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