SYZFAIL: posix_spawnp failed

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c64b3f32a570 umass: Add comment for ASC/ASCQ 24h/00h INVAL..
git tree: freebsd-src
console output: https://syzkaller.appspot.com/x/log.txt?x=125b45f8580000
dashboard link: https://syzkaller.appspot.com/bug?extid=7fb9542c410d3e919ef1
userspace arch: i386

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

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

SYZFAIL: posix_spawnp failed
(errno 35: Resource temporarily unavailable)
maxproc limit exceeded by uid 0 (pid 7612); see tuning(7) and login.conf(5)


FreeBSD/amd64 (ci-freebsd-i386-1.us-central1-b.c.syzkaller.internal) (ttyu0)

login: maxproc limit exceeded by uid 0 (pid 5715); see tuning(7) and login.conf(5)
set $lines = 0
Password:maxproc limit exceeded by uid 0 (pid 8854); see tuning(7) and login.conf(5)

Login incorrect
login: show registers
maxproc limit exceeded by uid 0 (pid 8854); see tuning(7) and login.conf(5)
Password:
maxproc limit exceeded by uid 0 (pid 9119); see tuning(7) and login.conf(5)
Login incorrect
login: ps
maxproc limit exceeded by uid 0 (pid 9119); see tuning(7) and login.conf(5)
Jan 1 00:03:37 ci-freebsd-i386-1 login[748]: 2 LOGIN FAILURES ON ttyu0
Password:
Login incorrect
login: maxproc limit exceeded by uid 0 (pid 8639); see tuning(7) and login.conf(5)
show malloc
Password:maxproc limit exceeded by uid 0 (pid 8639); see tuning(7) and login.conf(5)

Login incorrect
maxproc limit exceeded by uid 0 (pid 5803); see tuning(7) and login.conf(5)
maxproc limit exceeded by uid 0 (pid 5964); see tuning(7) and login.conf(5)


---
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.