linux-kernel - Re: [PATCH v2] kernel: add pid_max to 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] [day] [month] [year] [list]

Message-ID: <20241104113514.10625a03@gandalf.local.home>
Date: Mon, 4 Nov 2024 11:35:14 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Yun Zhou <yun.zhou@...driver.com>
Cc: <mcgrof@...nel.org>, <kees@...nel.org>, <joel.granados@...nel.org>,
 <mhiramat@...nel.org>, <mathieu.desnoyers@...icios.com>,
 <linux-kernel@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
 <linux-trace-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] kernel: add pid_max to pid_namespace

On Mon, 4 Nov 2024 08:54:08 +0800
Yun Zhou <yun.zhou@...driver.com> 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 <yun.zhou@...driver.com>

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/

- 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