pool: free list modified: mbufpl (6)

[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=1558e8ba580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=d1ee6fa33c143124fc6d

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+d1ee6f...@syzkaller.appspotmail.com

panic: pool_p_free: mbufpl free list modified: page 0xfffffd806a11d000; item addr 0xfffffd806a11d100; offset 0x0=0x0
Starting stack trace...
panic(ffffffff833e9328) at panic+0x1ba sys/kern/subr_prf.c:229
pool_p_free(ffffffff839552f0,fffffd806ba1ad28) at pool_p_free+0x28c sys/kern/subr_pool.c:1009
pool_reclaim(ffffffff839552f0) at pool_reclaim+0x2c2 sys/kern/subr_pool.c:1156
pool_reclaim_all() at pool_reclaim_all+0x48 sys/kern/subr_pool.c:-1
kern_sysctl(ffff80003c94d614,1,0,ffff80003c94d648,200000001440,4,8fc5b46d79b025c8) at kern_sysctl+0x1094 sys/kern/kern_sysctl.c:687
sys_sysctl(ffff8000324d4fb8,ffff80003c94d770,ffff80003c94d6c0) at sys_sysctl+0x3e5 sys/kern/kern_sysctl.c:-1
syscall(ffff80003c94d770) at syscall+0x962 mi_syscall sys/sys/syscall_mi.h:-1 [inline]
syscall(ffff80003c94d770) at syscall+0x962 sys/arch/amd64/amd64/trap.c:783
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x2d1776f82c0, 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