Hmm, I had hoped that I made that clear in the article, sorry that I didn't. When a process does a setuid() to another user, it needs to "fit" in the new user's RLIMIT_NPROC (or else users can evade that limit by way of setuid programs). So, when a privileged process changes its UID by way of setuid(), something needs to be done to enforce RLIMIT_NPROC. Failing the setuid() itself can cause problems with badly written programs, so these patches are ways to enforce that limit without returning an error from setuid().