From: Andrew Morton <akpm@linux-foundation.org>
To: Andrey Vagin <avagin@openvz.org>
Cc: linux-kernel@vger.kernel.org, criu@openvz.org,
Oleg Nesterov <oleg@redhat.com>, Robin Holt <holt@sgi.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Chen Gang <gang.chen@asianux.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Pavel Emelyanov <xemul@parallels.com>,
Aditya Kali <adityakali@google.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] kernel: reduce required permission for prctl_set_mm
Date: Wed, 12 Feb 2014 13:32:28 -0800 [thread overview]
Message-ID: <20140212133228.e4ff66c6add0c6b121232aad@linux-foundation.org> (raw)
In-Reply-To: <1392219611-13260-1-git-send-email-avagin@openvz.org>
On Wed, 12 Feb 2014 19:40:11 +0400 Andrey Vagin <avagin@openvz.org> wrote:
> Currently prctl_set_mm requires the global CAP_SYS_RESOURCE,
> this patch reduce requiremence to CAP_SYS_RESOURCE in the current
> namespace.
>
> When we restore a task we need to set up text, data and data heap sizes
> from userspace to the values a task had at checkpoint time.
>
> Currently we can not restore these parameters, if a task lives in
> a non-root user name space, because it has no capabilities in the
> parent namespace.
>
> prctl_set_mm() changes parameters of the current task and doesn't affect
> other tasks.
>
> This patch affects the RLIMIT_DATA limit, because a consumtiuon is
> calculated relatively to mm->end_data, mm->start_data, mm->start_brk.
I can't for the life of me work out what you were trying to say here.
Please fix and resend this paragraph?
> rlim = rlimit(RLIMIT_DATA);
> if (rlim < RLIM_INFINITY && (brk - mm->start_brk) +
> (mm->end_data - mm->start_data) > rlim)
> goto out;
>
> This limit affects calls to brk() and sbrk(), but it doesn't affect
> mmap. So I think requirement of CAP_SYS_RESOURCE in the current
> namespace is enough for this limit.
>
> ...
>
> Cc: security@kernel.org
That list is for reporting kernel security bugs.
>
> --- a/kernel/sys.c
> +++ b/kernel/sys.c
> @@ -1701,7 +1701,7 @@ static int prctl_set_mm(int opt, unsigned long addr,
> if (arg5 || (arg4 && opt != PR_SET_MM_AUXV))
> return -EINVAL;
>
> - if (!capable(CAP_SYS_RESOURCE))
> + if (!ns_capable(current_user_ns(), CAP_SYS_RESOURCE))
> return -EPERM;
>
> if (opt == PR_SET_MM_EXE_FILE)
This looks harmless.
My relatively-up-to-date manpages don't mention prctl(PR_SET_MM). I
see from http://marc.info/?l=linux-man&m=133132612704130&w=2 that
manpage additions were prepared nearly three years ago. Michael, did
this fall through a crack?
next prev parent reply other threads:[~2014-02-12 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 15:40 Andrey Vagin
2014-02-12 21:32 ` Andrew Morton [this message]
2014-02-12 21:50 ` Kees Cook
2014-02-12 23:08 ` Andrew Vagin
2014-02-12 21:55 ` [CRIU] " Cyrill Gorcunov
2014-02-12 22:11 ` Andrew Vagin
2014-02-12 23:14 ` 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=20140212133228.e4ff66c6add0c6b121232aad@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adityakali@google.com \
--cc=avagin@openvz.org \
--cc=criu@openvz.org \
--cc=ebiederm@xmission.com \
--cc=gang.chen@asianux.com \
--cc=holt@sgi.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®