From: Andrey Vagin <avagin@openvz.org>
To: linux-kernel@vger.kernel.org
Cc: criu@openvz.org, Andrey Vagin <avagin@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Pavel Emelyanov <xemul@parallels.com>,
Aditya Kali <adityakali@google.com>
Subject: [PATCH RFC 0/3] c/r: add ability to restore mm attributes in a non-root userns
Date: Fri, 14 Feb 2014 18:13:26 +0400 [thread overview]
Message-ID: <1392387209-330-1-git-send-email-avagin@openvz.org> (raw)
Currently PR_SET_MM_* require the global CAP_SYS_RESOURCE,
which is absent in a non-root userns.
Here are three groups of attributes:
1. PR_SET_MM_START_*_DATA, PR_SET_MM_*BRK, PR_SET_MM_*_STACK
These attributes can affect resource limits, so here is no sense
to restrict them if a proper limit is unlimited.
2. PR_MM_SET_EXE_FILE. We have not found other way than add
a secure bit. This bit is set from a root userns and inhereted by
children. Thanks to Pavel Emelyanov for the idea.
3. All other attributes don't affect other tasks or limits, so
can be changed without special permissions.
Andrey Vagin (3):
prctl: reduce permissions to change boundaries of data, brk and stack
capabilities: add a secure bit to allow changing a task exe link
prctl: allow to use PR_MM_SET_* which affect only a current task
include/uapi/linux/securebits.h | 9 ++++++++-
kernel/sys.c | 21 +++++++++++++++++++--
kernel/user_namespace.c | 3 ++-
security/commoncap.c | 7 +++++++
4 files changed, 36 insertions(+), 4 deletions(-)
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Kees Cook <keescook@chromium.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Pavel Emelyanov <xemul@parallels.com>
Cc: Aditya Kali <adityakali@google.com>
--
1.8.5.3
next reply other threads:[~2014-02-14 14:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 14:13 Andrey Vagin [this message]
2014-02-14 14:13 ` [PATCH 1/3] prctl: reduce permissions to change boundaries of data, brk and stack Andrey Vagin
2014-02-14 16:05 ` Eric W. Biederman
2014-02-14 17:43 ` Andrew Vagin
2014-02-14 18:01 ` [CRIU] " Cyrill Gorcunov
2014-02-14 19:16 ` Eric W. Biederman
2014-02-14 19:47 ` Pavel Emelyanov
2014-02-14 20:06 ` Cyrill Gorcunov
2014-02-14 20:18 ` Eric W. Biederman
2014-02-15 6:29 ` Cyrill Gorcunov
2014-02-15 23:01 ` Eric W. Biederman
2014-02-14 20:09 ` Eric W. Biederman
2014-02-17 8:34 ` Pavel Emelyanov
2014-02-17 8:52 ` Cyrill Gorcunov
2014-02-17 16:57 ` Pavel Emelyanov
2014-03-07 13:51 ` Pavel Emelyanov
2014-02-14 20:44 ` Andrey Wagin
2014-02-15 23:05 ` Eric W. Biederman
2014-02-14 14:13 ` [PATCH 2/3] capabilities: add a secure bit to allow changing a task exe link Andrey Vagin
2014-02-18 4:53 ` Serge E. Hallyn
2014-02-14 14:13 ` [PATCH 3/3] prctl: allow to use PR_MM_SET_* which affect only a current task Andrey 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=1392387209-330-1-git-send-email-avagin@openvz.org \
--to=avagin@openvz.org \
--cc=adityakali@google.com \
--cc=akpm@linux-foundation.org \
--cc=criu@openvz.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.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 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.