panic: kernel diagnostic assertion "pg->wire_count == NUM" failed

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b0e7aced8b61 Simplify EC_get_builtin_curves().
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=137d5240580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=d113566386be5479a185

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0a6fe75c7bb2/disk-b0e7aced.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/ebe2772bacfb/bsd-b0e7aced.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/02713b07760a/kernel-b0e7aced.xz

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

panic: kernel diagnostic assertion "pg->wire_count == 1" failed
: file "/syzkaller/managers/main/kernel/sys/kern/vfs_biomem.c",
line 310
Starting stack trace...
panic(ffffffff830b03bc) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff8306a3b3,ffffffff83074a33,136,ffffffff82ff3e34) at __assert+0x29
buf_free_pages(fffffd806f1bfc10) at buf_free_pages+0x23d sys/kern/vfs_biomem.c:299
buf_dealloc_mem(fffffd806f1bfc10) at buf_dealloc_mem+0x14e sys/kern/vfs_biomem.c:179
buf_put(fffffd806f1bfc10) at buf_put+0x1dc sys/kern/vfs_bio.c:127
brelse(fffffd806f1bfc10) at brelse+0x395 sys/kern/vfs_bio.c:944
vinvalbuf(fffffd80691d3cb8,2,ffffffffffffffff,ffff80002a5211f8,0,ffffffffffffffff) at vinvalbuf+0x52c sys/kern/vfs_subr.c:2022
ffs_truncate(fffffd805df781e0,0,0,ffffffffffffffff) at ffs_truncate+0xf63
ufs_inactive(ffff80002a55f2e8) at ufs_inactive+0x203 sys/ufs/ufs/ufs_inode.c:84
VOP_INACTIVE(fffffd80691d3cb8,ffff80002a5211f8) at VOP_INACTIVE+0xfe sys/kern/vfs_vops.c:495
vrele(fffffd80691d3cb8) at vrele+0x120 sys/kern/vfs_subr.c:824
ktrwriteraw(ffff80002a5211f8,fffffd80691d3cb8,fffffd807f7d7888,ffff80002a55f480,ffff80002a55f460) at ktrwriteraw+0x352 ktrcleartrace sys/kern/kern_ktrace.c:86 [inline]
ktrwriteraw(ffff80002a5211f8,fffffd80691d3cb8,fffffd807f7d7888,ffff80002a55f480,ffff80002a55f460) at ktrwriteraw+0x352 sys/kern/kern_ktrace.c:701
ktrsyscall(ffff80002a5211f8,4a,18,ffff80002a55f610) at ktrsyscall+0x31d sys/kern/kern_ktrace.c:182
syscall(ffff80002a55f610) at syscall+0x2ad mi_syscall sys/sys/syscall_mi.h:156 [inline]
syscall(ffff80002a55f610) at syscall+0x2ad sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x73f103880d70, count: 242
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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.