From: Oleg Nesterov <oleg@redhat.com>
To: Adrian Reber <areber@redhat.com>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
Eric Biederman <ebiederm@xmission.com>,
Pavel Emelyanov <ovzxemul@gmail.com>,
Jann Horn <jannh@google.com>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Andrei Vagin <avagin@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>,
Radostin Stoyanov <rstoyanov1@gmail.com>
Subject: Re: [PATCH v11 1/2] fork: extend clone3() to support setting a PID
Date: Fri, 15 Nov 2019 17:33:09 +0100 [thread overview]
Message-ID: <20191115163308.GC25528@redhat.com> (raw)
In-Reply-To: <20191115123621.142252-1-areber@redhat.com>
On 11/15, Adrian Reber wrote:
>
> v11:
> - abort alloc_pid() correctly if one of the PIDs specified in
> set_pid[] is invalid (Andrei)
> ---
> include/linux/pid.h | 3 +-
> include/linux/pid_namespace.h | 2 +
> include/linux/sched/task.h | 3 ++
> include/uapi/linux/sched.h | 53 +++++++++++++++++---------
> kernel/fork.c | 24 +++++++++++-
> kernel/pid.c | 72 +++++++++++++++++++++++++++--------
> kernel/pid_namespace.c | 2 -
> 7 files changed, 122 insertions(+), 37 deletions(-)
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2019-11-15 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 12:36 [PATCH v11 1/2] fork: extend clone3() to support setting a PID Adrian Reber
2019-11-15 12:36 ` [PATCH v11 2/2] selftests: add tests for clone3() with *set_tid Adrian Reber
2019-11-15 22:20 ` Andrei Vagin
2019-11-15 22:53 ` Christian Brauner
2019-11-18 1:46 ` Andrei Vagin
2019-11-18 7:42 ` Christian Brauner
2019-11-15 16:33 ` Oleg Nesterov [this message]
2019-11-15 16:54 ` [PATCH v11 1/2] fork: extend clone3() to support setting a PID Dmitry Safonov
2019-11-15 17:02 ` Dmitry Safonov
2019-11-15 22:51 ` Christian Brauner
2019-11-15 21:54 ` Andrei Vagin
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=20191115163308.GC25528@redhat.com \
--to=oleg@redhat.com \
--cc=0x7f454c46@gmail.com \
--cc=areber@redhat.com \
--cc=avagin@gmail.com \
--cc=christian.brauner@ubuntu.com \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ovzxemul@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=rstoyanov1@gmail.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