panic: missing alias (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: db5d28f093d6 Bump kcov buffer size limit
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=16e175f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7058272de1526588
dashboard link: https://syzkaller.appspot.com/bug?extid=2eaddfd8647a34a44071

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/daa0f9ba3aa0/disk-db5d28f0.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/da471e678042/bsd-db5d28f0.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fca6ec5e4a2d/kernel-db5d28f0.xz

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

panic: missing alias
Starting stack trace...
panic(ffffffff83050e63) at panic+0x1d0 sys/kern/subr_prf.c:229
vgonel(fffffd80617d5cf0,ffff80002a52cf68) at vgonel+0x681 sys/kern/vfs_subr.c:1218
vrecycle(fffffd80617d5cf0,ffff80002a52cf68) at vrecycle+0x7c sys/kern/vfs_subr.c:1144
ufs_inactive(ffff80002a4baf78) at ufs_inactive+0x360 sys/ufs/ufs/ufs_inode.c:107
VOP_INACTIVE(fffffd80617d5cf0,ffff80002a52cf68) at VOP_INACTIVE+0x107 sys/kern/vfs_vops.c:495
vput(fffffd80617d5cf0) at vput+0xe5 sys/kern/vfs_subr.c:797
VOP_REMOVE(fffffd805f0b21f8,fffffd80617d5cf0,ffff80002a4bb0f8) at VOP_REMOVE+0x19d sys/kern/vfs_vops.c:336
dounlinkat(ffff80002a52cf68,ffffff9c,7446a1e2e600,0) at dounlinkat+0x177 sys/kern/vfs_syscalls.c:1887
syscall(ffff80002a4bb270) at syscall+0xb08 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80002a4bb270) at syscall+0xb08 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7446a1e2eab0, 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