panic: kernel diagnostic assertion "ps->ps_uvncount == NUM" failed: file "

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 33a257f813d9 It helps to commit the actual test scripts...
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=11744540580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=9f3e651f26f4dee889f6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f0ed2bb59e11/disk-33a257f8.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/0c53daba5dee/bsd-33a257f8.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6fbaad38bce6/kernel-33a257f8.xz

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

panic: kernel diagnostic assertion "ps->ps_uvncount == 0" failed: file "
/syzkaller/managers/main/kernel/sys/kern/kern_unveil.c", line 188
Starting stack trace...
panic(ffffffff830b5f6d) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff8306b5a4,ffffffff8303e84c,bc,ffffffff82ff1787) at __assert+0x29
unveil_destroy(ffff8000376aa6a8) at unveil_destroy+0x1dd sys/kern/kern_unveil.c:188
exit1(ffff80002a4d1200,0,0,1) at exit1+0x60f sys/kern/kern_exit.c:233
sys_exit(ffff80002a4d1200,ffff80002a59bbb0,ffff80002a59bb00) at sys_exit+0x1a
syscall(ffff80002a59bbb0) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7c1547296cc0, 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

[syzbot]

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