linux-kernel - Re: [PATCH 2/3] kernel/pid: Remove default pid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Mon, 8 Apr 2024 13:29:55 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Michal Koutný <mkoutny@...e.com>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Steven
 Rostedt <rostedt@...dmis.org>, Masami Hiramatsu <mhiramat@...nel.org>,
 Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Christian Brauner
 <brauner@...nel.org>, Oleg Nesterov <oleg@...hat.com>, Kent Overstreet
 <kent.overstreet@...ux.dev>, Kees Cook <keescook@...omium.org>, Tycho
 Andersen <tandersen@...flix.com>, Jens Axboe <axboe@...nel.dk>, Aleksa
 Sarai <cyphar@...har.com>
Subject: Re: [PATCH 2/3] kernel/pid: Remove default pid_max value

On Mon,  8 Apr 2024 16:58:18 +0200 Michal Koutný <mkoutny@...e.com> wrote:

> 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.
> 
> This change thus increases initial pid_max from 32k to 4M (x86_64
> defconfig).

That seems like a large change.

It isn't clear why we'd want to merge this patchset.  Does it improve
anyone's life and if so, how?