panic: kernel diagnostic assert

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ff46e7d6ebc3 remove struct arpreq from net/if_arp.h
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=1122845f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=09e8b2f90df8070273b6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2daa6bbf955f/disk-ff46e7d6.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/c2ca98fd46b5/bsd-ff46e7d6.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f593ecafacdf/kernel-ff46e7d6.xz

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

panic: kernel diagnostic assert
ion "ps->ps_uvncount == 0" fail
ed: file "/syzkaller/managers/m
ain/kernel/sys/kern/kern_unveil
.c", line 188
Starting stack trace...
panic(ffffffff830b549f) at panic+0x1ba sys/kern/subr_prf.c:229
__assert(ffffffff83068c58,ffffffff83035827,bc,ffffffff82fe89a9) at __assert+0x29
unveil_destroy(ffff80002a5a2b08) at unveil_destroy+0x1dd sys/kern/kern_unveil.c:188
exit1(ffff800037616530,b,0,1) at exit1+0x60f sys/kern/kern_exit.c:233
sys_exit(ffff800037616530,ffff80002a57d290,ffff80002a57d1e0) at sys_exit+0x1a

syscall(ffff80002a57d290) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x756efcf4d6e0, count: 250
End of stack trace.
syncing disks...set $lines = 0
set $maxwidth = 0
show panic
trace
show registers
show proc
ps
show all locks
show malloc
show all pools
machine ddbcpu 0
trace
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.

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.