TL;DR excerpt from commit 02/03:
The kernel provides mechanisms, while it should not imply policies --
default pid_max seems to be an example of the policy that does not fit
all. At the same time pid_max must have some value assigned, so use the
end of the allowed range -- pid_max_max.
More details are in that commit's message. The other two commits are
related preparation and less related refresh in code that somewhat
references pid_max.
Michal Koutný (3):
tracing: Remove dependency of saved_cmdlines_buffer on PID_MAX_DEFAULT
kernel/pid: Remove default pid_max value
tracing: Compare pid_max against pid_list capacity
include/linux/pid.h | 4 ++--
include/linux/threads.h | 15 ++++-----------
kernel/pid.c | 8 +++-----
kernel/trace/pid_list.c | 6 +++---
kernel/trace/pid_list.h | 4 ++--
kernel/trace/trace_sched_switch.c | 11 ++++++-----
6 files changed, 20 insertions(+), 28 deletions(-)
base-commit: fec50db7033ea478773b159e0e2efb135270e3b7
--
2.44.0
