syzbot


panic: chgproccnt: procs < NUM

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

Sample crash report:
panic: chgproccnt: procs < 0
Starting stack trace...
panic(ffffffff8335b716) at panic+0x1d0 sys/kern/subr_prf.c:229
chgproccnt(ee00,ffffffff) at chgproccnt+0xcc sys/kern/kern_proc.c:171
sys_setreuid(ffff80002a393220,ffff80003681f5e0,ffff80003681f530) at sys_setreuid+0x587 sys/kern/kern_prot.c:688
syscall(ffff80003681f5e0) at syscall+0xb08 mi_syscall sys/sys/syscall_mi.h:176 [inline]
syscall(ffff80003681f5e0) at syscall+0xb08 sys/arch/amd64/amd64/trap.c:579
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0x7e13f7084f0, count: 252
End of stack trace.

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/18 01:39 openbsd 7cbb080c3e94 e77fae15 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: chgproccnt: procs < NUM
2025/05/17 15:40 openbsd 007267a8c99a f41472b0 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: chgproccnt: procs < NUM
2025/05/12 09:11 openbsd 1d7d4b26237d 77908e5f .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: chgproccnt: procs < NUM
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.