Re: [PATCH 2/2] pid: Optional first-fit pid allocation

On Sat, Feb 22, 2025 at 09:02:08AM +0000, David Laight [off-list ref] wrote:

It also seems a good way of being able to predict the next pid and
doing all the 'nasty' things that allows because there is no guard
time on pid reuse.

The motivations was not to make guessing next pid more difficult, I'll
update the docs with better explanation.

Both first-fit and next-fit have the same issue.
Picking a random pid is better.

I surely don't want to delve into this now. (I acknowledge that having a
possible range specified per pid ns would be useful for such a
randomization.)

Michal