panic: semexit - semid not allocated

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8b4580606d31 Turn off scrollbar when pane is in alternate ..
git tree: openbsd
console output: https://syzkaller.appspot.com/x/log.txt?x=10d271a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bc15e68cd2a49e5
dashboard link: https://syzkaller.appspot.com/bug?extid=9166ddaad8653c5dadff

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/beb5b4bdd045/disk-8b458060.raw.xz
bsd.gdb: https://storage.googleapis.com/syzbot-assets/a9232755dfc2/bsd-8b458060.gdb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0efc19029231/kernel-8b458060.xz

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

panic: semexit - semid not allocated
Starting stack trace...
panic(ffffffff830511a6) at panic+0x1ba sys/kern/subr_prf.c:229
semexit(ffff80002a464898) at semexit+0x25c sys/kern/sysv_sem.c:825
exit1(ffff80002a4c2038,0,0,1) at exit1+0x5ab sys/kern/kern_exit.c:220
sys_exit(ffff80002a4c2038,ffff80002a573bd0,ffff80002a573b20) at sys_exit+0x1a
syscall(ffff80002a573bd0) at syscall+0x97e sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x78415b5bfc90, count: 251
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.