syzbot


panic: chgproccnt: procs < NUM

Status: upstream: reported on 2025/02/22 06:58
Reported-by: syzbot+265d5006dac2f45c9e9d@syzkaller.appspotmail.com
First crash: 14h33m, last: 14h33m

Sample crash report:
panic: chgproccnt: procs < 0
Starting stack trace...
panic(ffffffff83330c29) at panic+0x1d0 sys/kern/subr_prf.c:229
chgproccnt(4000,ffffffff) at chgproccnt+0xcc sys/kern/kern_proc.c:171
sys_setreuid(ffff80003c0d8028,ffff8000390c8040,ffff8000390c7f90) at sys_setreuid+0x587 sys/kern/kern_prot.c:688
syscall(ffff8000390c8040) at syscall+0xb08 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff8000390c8040) at syscall+0xb08 sys/arch/amd64/amd64/trap.c:577
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x775f93dc080, count: 252
End of stack trace.

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/22 06:57 openbsd 6a403588e274 d34966d1 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: chgproccnt: procs < NUM
* Struck through repros no longer work on HEAD.