Thread (2 messages) 2 messages, 2 authors, 2024-11-04

Re: [PATCH v2] kernel: add pid_max to pid_namespace

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2024-11-04 16:35:16
Also in: linux-fsdevel, lkml

On Mon, 4 Nov 2024 08:54:08 +0800
Yun Zhou [off-list ref] wrote:
It is necessary to have a different pid_max in different containers.
For example, multiple containers are running on a host, one of which
is Android, and its 32 bit bionic libc only accepts pid <= 65535. So
it requires the global pid_max <= 65535. This will cause configuration
conflicts with other containers and also limit the maximum number of
tasks for the entire system.

Signed-off-by: Yun Zhou <redacted>
I acked the first patch. You don't mention what's different about this one
(which is something you should do below the '---' line and above the diffstat.

Like:

Changes since v1: https://lore.kernel.org/all/20241030052933.1041408-1-yun.zhou@windriver.com/ (local)

- Describe what is different.

What changed? Is it big enough for me to re-review this one so that my ack
needs to be reevaluated?

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help