panic: pool_do_get: pkpcb: page empty

0 views
Skip to first unread message

syzbot

unread,
Apr 21, 2024, 5:27:18 AMApr 21
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a0c63bf7b3c7 Remove more unnecessary GOST code
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=172a67cb180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=98a93366cf9c5cde8d33

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/83eeec7794ed/disk-a0c63bf7.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/689cc4b68604/bsd-a0c63bf7.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ab50c1488b02/kernel-a0c63bf7.xz

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

panic: pool_do_get: pkpcb: page empty
Starting stack trace...
panic(ffffffff82945c77) at panic+0x16f sys/kern/subr_prf.c:229
pool_do_get(ffffffff82d658d0,9,ffff800033b6e288) at pool_do_get+0x40f sys/kern/subr_pool.c:726
pool_get(ffffffff82d658d0,9) at pool_get+0xf0 sys/kern/subr_pool.c:582
pfkeyv2_attach(ffff800010fde7c8,0,1) at pfkeyv2_attach+0xb1 sys/net/pfkeyv2.c:284
socreate(1e,ffff800033b6e3b8,3,0) at socreate+0x1ab pru_attach sys/sys/protosw.h:278 [inline]
socreate(1e,ffff800033b6e3b8,3,0) at socreate+0x1ab sys/kern/uipc_socket.c:212
sys_socket(ffff80002a2279c8,ffff800033b6e510,ffff800033b6e460) at sys_socket+0xdc sys/kern/uipc_syscalls.c:101
syscall(ffff800033b6e510) at syscall+0x8cf mi_syscall sys/sys/syscall_mi.h:180 [inline]
syscall(ffff800033b6e510) at syscall+0x8cf sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x34555c49f80, 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