From: Serge Hallyn <serge.hallyn@ubuntu.com>
To: Glauber Costa <glommer@parallels.com>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] kernel: allow reboots from user_ns
Date: Thu, 14 Feb 2013 08:27:45 -0600 [thread overview]
Message-ID: <20130214142745.GA4470@sergelap> (raw)
In-Reply-To: <1360843000-31228-1-git-send-email-glommer@parallels.com>
Quoting Glauber Costa (glommer@parallels.com):
> Reboot support for pid namespaces is already implemented and it works
> well. However, in most containers the tasks will join all namespaces,
> including the now supported user namespace. In that situation, we will
> fail the "capable" test and won't be able to reboot.
>
> The proposed solution is to allow reboots for CAP_SYS_BOOT processes
> in the user namespace that owns the pid namespace.
>
> Signed-off-by: Glauber Costa <glommer@parallels.com>
Note Li Zefan sent this identical patch last year. It's in my own
built userns kernel, and definately required :)
In any case,
Acked-by: Serge E. Hallyn <serge.hallyn@ubuntu.com>
> Cc: Eric W. Biederman <ebiederm@xmission.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
> kernel/sys.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sys.c b/kernel/sys.c
> index 265b376..3b0958e 100644
> --- a/kernel/sys.c
> +++ b/kernel/sys.c
> @@ -435,9 +435,10 @@ SYSCALL_DEFINE4(reboot, int, magic1, int, magic2, unsigned int, cmd,
> {
> char buffer[256];
> int ret = 0;
> + struct pid_namespace *curr_pidns = task_active_pid_ns(current);
>
> /* We only trust the superuser with rebooting the system. */
> - if (!capable(CAP_SYS_BOOT))
> + if (!ns_capable(curr_pidns->user_ns, CAP_SYS_BOOT))
> return -EPERM;
>
> /* For safety, we require "magic" arguments. */
> @@ -453,7 +454,7 @@ SYSCALL_DEFINE4(reboot, int, magic1, int, magic2, unsigned int, cmd,
> * pid_namespace, the command is handled by reboot_pid_ns() which will
> * call do_exit().
> */
> - ret = reboot_pid_ns(task_active_pid_ns(current), cmd);
> + ret = reboot_pid_ns(curr_pidns, cmd);
> if (ret)
> return ret;
>
> --
> 1.8.1.2
>
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2013-02-14 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 11:56 [PATCH] kernel: allow reboots from user_ns Glauber Costa
2013-02-14 11:56 ` Glauber Costa
[not found] ` <1360843000-31228-1-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-02-14 12:08 ` Daniel Lezcano
2013-02-14 12:08 ` Daniel Lezcano
2013-02-14 14:27 ` Serge Hallyn
2013-02-14 14:27 ` Serge Hallyn [this message]
2013-02-14 14:30 ` Glauber Costa
2013-02-14 14:30 ` Glauber Costa
[not found] ` <511CF51C.6050504-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-02-14 14:58 ` Eric W. Biederman
2013-02-14 14:58 ` Eric W. Biederman
[not found] ` <87wqubc58b.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2013-02-15 7:00 ` Glauber Costa
2013-02-15 7:00 ` Glauber Costa
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=20130214142745.GA4470@sergelap \
--to=serge.hallyn@ubuntu.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=glommer@parallels.com \
--cc=linux-kernel@vger.kernel.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.