From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Oleg Nesterov <oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH review 0/3] pid namespaces fixes
Date: Fri, 21 Dec 2012 20:56:49 -0800 [thread overview]
Message-ID: <87d2y2elbi.fsf@xmission.com> (raw)
Oleg assuming I am not blind these patches should fix the issues you
spotted in the pid namespace as well as one additional one that I found
during testing.
Anyone with an extra set of eyeballs that wants to look over this code
and double check to make certain I am not doing something stupid would
be welcome.
These patches are against 3.8-rc1 and I hope to get the into linux-next
and on to Linus shortly.
Eric W. Biederman (3):
pidns: Outlaw thread creation after unshare(CLONE_NEWPID)
pidns: Stop pid allocation when init dies
proc: Allow proc_free_inum to be called from any context
fs/proc/generic.c | 13 +++++++------
include/linux/pid.h | 1 +
include/linux/pid_namespace.h | 4 +++-
kernel/fork.c | 8 ++++++++
kernel/pid.c | 13 ++++++++++---
kernel/pid_namespace.c | 4 ++++
6 files changed, 33 insertions(+), 10 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@redhat.com>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: [PATCH review 0/3] pid namespaces fixes
Date: Fri, 21 Dec 2012 20:56:49 -0800 [thread overview]
Message-ID: <87d2y2elbi.fsf@xmission.com> (raw)
Oleg assuming I am not blind these patches should fix the issues you
spotted in the pid namespace as well as one additional one that I found
during testing.
Anyone with an extra set of eyeballs that wants to look over this code
and double check to make certain I am not doing something stupid would
be welcome.
These patches are against 3.8-rc1 and I hope to get the into linux-next
and on to Linus shortly.
Eric W. Biederman (3):
pidns: Outlaw thread creation after unshare(CLONE_NEWPID)
pidns: Stop pid allocation when init dies
proc: Allow proc_free_inum to be called from any context
fs/proc/generic.c | 13 +++++++------
include/linux/pid.h | 1 +
include/linux/pid_namespace.h | 4 +++-
kernel/fork.c | 8 ++++++++
kernel/pid.c | 13 ++++++++++---
kernel/pid_namespace.c | 4 ++++
6 files changed, 33 insertions(+), 10 deletions(-)
next reply other threads:[~2012-12-22 4:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 4:56 Eric W. Biederman [this message]
2012-12-22 4:56 ` [PATCH review 0/3] pid namespaces fixes Eric W. Biederman
[not found] ` <87d2y2elbi.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-22 4:57 ` [PATCH review 1/3] pidns: Outlaw thread creation after unshare(CLONE_NEWPID) Eric W. Biederman
2012-12-22 4:57 ` Eric W. Biederman
[not found] ` <877goaela9.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-22 19:39 ` Rob Landley
2012-12-22 19:39 ` Rob Landley
2012-12-22 20:16 ` Eric W. Biederman
2012-12-22 20:16 ` Eric W. Biederman
2012-12-22 4:58 ` [PATCH review 2/3] pidns: Stop pid allocation when init dies Eric W. Biederman
2012-12-22 4:58 ` Eric W. Biederman
[not found] ` <871ueiel9d.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-22 16:54 ` Oleg Nesterov
2012-12-22 16:54 ` Oleg Nesterov
[not found] ` <20121222165438.GA19680-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-12-22 20:31 ` Eric W. Biederman
2012-12-22 20:31 ` Eric W. Biederman
2012-12-25 8:24 ` [PATCH review 2/3 take 2] " Eric W. Biederman
2012-12-25 8:24 ` Eric W. Biederman
[not found] ` <87licm7d4n.fsf_-_-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-25 16:59 ` Oleg Nesterov
2012-12-25 16:59 ` Oleg Nesterov
2012-12-22 4:58 ` [PATCH review 3/3] proc: Allow proc_free_inum to be called from any context Eric W. Biederman
2012-12-22 4:58 ` Eric W. Biederman
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=87d2y2elbi.fsf@xmission.com \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=oleg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.