panic: pool_do_get: filepl: page empty

0 views
Skip to first unread message

syzbot

unread,
Apr 17, 2024, 1:28:27 AMApr 17
to syzkaller-o...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 489289b76a3a Revert wip patch, not intended for commit
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=126424e7180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=d8b582be9f7185e656ba

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/563ad16c05c2/disk-489289b7.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/fe28af3e55ed/bsd-489289b7.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/23f067429599/kernel-489289b7.xz

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

panic: pool_do_get: filepl: page empty
Starting stack trace...
panic(ffffffff82947b5c) at panic+0x16f sys/kern/subr_prf.c:229
pool_do_get(ffffffff82e3c650,9,ffff80002d8a5878) at pool_do_get+0x40f sys/kern/subr_pool.c:726
pool_get(ffffffff82e3c650,9) at pool_get+0xf0 sys/kern/subr_pool.c:582
falloc(ffff800030ae34b0,ffff80002d8a5970,ffff80002d8a597c) at falloc+0x122 fnew sys/kern/kern_descrip.c:1046 [inline]
falloc(ffff800030ae34b0,ffff80002d8a5970,ffff80002d8a597c) at falloc+0x122 sys/kern/kern_descrip.c:1020
sys_socket(ffff800030ae34b0,ffff80002d8a5ab0,ffff80002d8a5a00) at sys_socket+0x172 sys/kern/uipc_syscalls.c:106
syscall(ffff80002d8a5ab0) at syscall+0x8cf mi_syscall sys/sys/syscall_mi.h:180 [inline]
syscall(ffff80002d8a5ab0) at syscall+0x8cf sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xdc5d2436570, count: 250
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