panic: pool_do_get: pfstlim: page empty

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: fd49698d88e5 Add support for RK3576 clocks and resets. A c..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=112ed75a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=dcbd08af335f20af4e3b

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c159f2fe1cb1/disk-fd49698d.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/d321f1e712d8/bsd-fd49698d.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0df89642a17a/kernel-fd49698d.xz

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

panic: pool_do_get: pfstlim: page empty
Starting stack trace...
panic(ffffffff833b8dff) at panic+0x1ba sys/kern/subr_prf.c:229
pool_do_get(ffffffff83a6dba0,9,ffff80003c95ab68) at pool_do_get+0x537 sys/kern/subr_pool.c:732
pool_get(ffffffff83a6dba0,9) at pool_get+0x11a sys/kern/subr_pool.c:-1
pf_statelim_add(ffff80003c95af40) at pf_statelim_add+0x16b sys/net/pf_ioctl.c:-1
pfioctl(24900,80804465,ffff80003c95af40,2,ffff8000318d0548) at pfioctl+0x2f94 sys/net/pf_ioctl.c:2283
VOP_IOCTL(fffffd805f85be78,80804465,ffff80003c95af40,2,fffffd8007ffd680,ffff8000318d0548) at VOP_IOCTL+0xa3 sys/kern/vfs_vops.c:264
vn_ioctl(fffffd806d156010,80804465,ffff80003c95af40,ffff8000318d0548) at vn_ioctl+0xea sys/kern/vfs_vnops.c:531
sys_ioctl(ffff8000318d0548,ffff80003c95b110,ffff80003c95b060) at sys_ioctl+0x660 sys/kern/sys_generic.c:-1
syscall(ffff80003c95b110) at syscall+0x962 mi_syscall sys/sys/syscall_mi.h:-1 [inline]
syscall(ffff80003c95b110) at syscall+0x962 sys/arch/amd64/amd64/trap.c:783
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xef379fec4b0, count: 247
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