panic: missing alias (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e82b5ebce50c Rework garbage collector for unix(4) sockets.
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=15d28e5db00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fe55924c11e64b0a
dashboard link: https://syzkaller.appspot.com/bug?extid=42f214a510dd62d4e4a7

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

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

panic: missing alias
Starting stack trace...
panic(ffffffff8245ea63) at panic+0x155 sys/kern/subr_prf.c:233
vgonel(fffffd8070301e78,ffff8000249167e8) at vgonel+0x4f8 sys/kern/vfs_subr.c:1175
vrecycle(fffffd8
070301e78,ffff8000249167e8) at vrecycle+0x54 sys/kern/vfs_subr.c:1102
ufs_inactive(ffff8000230fd2f8) at ufs_inactive+0x2ae sys/ufs/ufs/ufs_inode.c:122
VOP_INACTIVE(fffffd8070301e78,ffff8000249167e8) at VOP_INACTIVE+0xb7 sys/kern/vfs_vops.c:505
vput(fffffd8070301e78) at vput+0xad sys/kern/vfs_subr.c:779
vn_closefile(fffffd8065434690,ffff8000249167e8) at vn_closefile+0xdd sys/kern/vfs_vnops.c:626
fdrop(fffffd8065434690,ffff8000249167e8) at fdrop+0xc7 sys/kern/kern_descrip.c:1279
closef(fffffd8065434690,ffff8000249167e8) at closef+0x117 sys/kern/kern_descrip.c:1263
fdfree(ffff8000249167e8) at fdfree+0xf3 sys/kern/kern_descrip.c:1195
exit1(ffff8000249167e8,0,0,1) at exit1+0x35d sys/kern/kern_exit.c:202
sys_exit(ffff8000249167e8,ffff8000230fd5a0,ffff8000230fd600) at sys_exit+0x16 sys/kern/kern_exit.c:95
syscall(ffff8000230fd670) at syscall+0x44e sys/arch/amd64/amd64/trap.c:585
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7f7ffffeda40, count: 243
End of stack trace.
syncing disks...14 9 1 1 set $lines = 0
1 1 set $maxwidth = 0
1 show panic
1 trace
1 show registers
1 show proc
ps
1 show all locks
1 show malloc
show all pools
1 machine ddbcpu 0
trace
1 machine ddbcpu 1
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.

[syzbot]

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