From: Steven Rostedt <rostedt@goodmis.org>
To: Yun Zhou <yun.zhou@windriver.com>
Cc: <mcgrof@kernel.org>, <kees@kernel.org>,
<joel.granados@kernel.org>, <mhiramat@kernel.org>,
<mathieu.desnoyers@efficios.com>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] kernel: add pid_max to pid_namespace
Date: Tue, 12 Nov 2024 17:33:31 -0500 [thread overview]
Message-ID: <20241112173331.407a5be0@gandalf.local.home> (raw)
In-Reply-To: <20241105031024.3866383-1-yun.zhou@windriver.com>
On Tue, 5 Nov 2024 11:10:24 +0800
Yun Zhou <yun.zhou@windriver.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@windriver.com>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
> ---
> - Remove sentinels from ctl_table arrays.
> v1 - https://lore.kernel.org/all/20241030052933.1041408-1-yun.zhou@windriver.com/
> ---
> include/linux/pid_namespace.h | 1 +
> kernel/pid.c | 12 +++++------
> kernel/pid_namespace.c | 34 ++++++++++++++++++++++++++-----
> kernel/sysctl.c | 9 --------
> kernel/trace/pid_list.c | 2 +-
> kernel/trace/trace.h | 2 --
> kernel/trace/trace_sched_switch.c | 2 +-
> 7 files changed, 38 insertions(+), 24 deletions(-)
next prev parent reply other threads:[~2024-11-12 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 3:10 Yun Zhou
2024-11-12 22:33 ` Steven Rostedt [this message]
2024-11-19 9:15 ` Joel Granados
2024-11-20 9:06 ` Christian Brauner
2024-11-21 14:33 ` Tycho Andersen
2024-11-22 11:31 ` Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2024-11-04 0:54 Yun Zhou
2024-11-04 16:35 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241112173331.407a5be0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=yun.zhou@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®