From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: Christian Brauner <brauner@kernel.org>,
Shuah Khan <shuah@kernel.org>, Kees Cook <kees@kernel.org>,
David Hildenbrand <david@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Jan Kara <jack@suse.cz>, Aleksa Sarai <cyphar@cyphar.com>,
Andrei Vagin <avagin@google.com>, Kirill Tkhai <tkhai@ya.ru>,
Alexander Mikhalitsyn <alexander@mihalicyn.com>,
Adrian Reber <areber@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org
Subject: [PATCH 0/2] pid: make sub-init creation retryable
Date: Fri, 27 Feb 2026 13:02:03 +0100 [thread overview]
Message-ID: <aaGHu3ixbw9Y7kFj@redhat.com> (raw)
In-Reply-To: <20260225133229.550302-1-ptikhomirov@virtuozzo.com>
Andrew,
On top of Pavel's series but but doesn't depend on it.
Can be applied before or after.
Oleg.
---
kernel/fork.c | 6 +++++-
kernel/pid.c | 18 +++++++++++-------
2 files changed, 16 insertions(+), 8 deletions(-)
next prev parent reply other threads:[~2026-02-27 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 13:32 [PATCH v4 0/4] pid_namespace: make init creation more flexible Pavel Tikhomirov
2026-02-25 13:32 ` [PATCH v4 1/4] pid_namespace: avoid optimization of accesses to ->child_reaper Pavel Tikhomirov
2026-02-25 13:32 ` [PATCH v4 2/4] pid: check init is created first after idr alloc Pavel Tikhomirov
2026-02-25 18:46 ` Andrei Vagin
2026-02-25 13:32 ` [PATCH v4 3/4] pid_namespace: allow opening pid_for_children before init was created Pavel Tikhomirov
2026-02-25 18:38 ` Andrei Vagin
2026-02-25 13:32 ` [PATCH v4 4/4] selftests: Add tests for creating pidns init via setns Pavel Tikhomirov
2026-02-27 12:02 ` Oleg Nesterov [this message]
2026-02-27 12:03 ` [PATCH 1/2] pid: make sub-init creation retryable Oleg Nesterov
2026-02-27 12:04 ` [PATCH 2/2] pid: document the PIDNS_ADDING checks in alloc_pid() and copy_process() Oleg Nesterov
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=aaGHu3ixbw9Y7kFj@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander@mihalicyn.com \
--cc=areber@redhat.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=david@kernel.org \
--cc=jack@suse.cz \
--cc=juri.lelli@redhat.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=shuah@kernel.org \
--cc=tkhai@ya.ru \
--cc=vincent.guittot@linaro.org \
/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