syzbot


panic: semexit - semid not allocated

Status: upstream: reported on 2024/11/16 00:28
Reported-by: syzbot+9166ddaad8653c5dadff@syzkaller.appspotmail.com
First crash: 5d18h, last: 5d18h

Sample crash report:
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.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/16 00:27 openbsd 8b4580606d31 eeafb645 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-main panic: semexit - semid not allocated
* Struck through repros no longer work on HEAD.