From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: LKML <linux-kernel@vger.kernel.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Pavel Emelyanov <xemul@parallels.com>, Tejun Heo <tj@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] prctl: Use CAP_SYS_RESOUCE for PR_SET_MM option
Date: Thu, 8 Mar 2012 00:33:04 +0400 [thread overview]
Message-ID: <20120307203304.GB6215@moon> (raw)
In-Reply-To: <1331152168.1798.13.camel@x61.thuisdomein>
On Wed, Mar 07, 2012 at 09:29:28PM +0100, Paul Bolle wrote:
> On Wed, 2012-03-07 at 16:52 +0400, Cyrill Gorcunov wrote:
> > CAP_SYS_ADMIN is already overloaded left and right,
> > so to have more finegrained access control use
> > CAP_SYS_RESOUCE here.
> >
> > The CAP_SYS_RESOUCE is chosen because this prctl
> > option allows a current process to adjust some
> > fields of memory map descriptor which rather
> > represent what the process owns: pointers to
> > code, data, stack segments, command line,
> > auxilary vector data and etc.
>
> Nitpicking: s/CAP_SYS_RESOUCE/CAP_SYS_RESOURCE/ in both the commit
> summary and the commit explanation. (And if you change that you might
> also do a s/auxilary/auxiliary/ in the commit explanation.)
Oh, crap! Thanks Paul, patch was unrefreshed, while I was testing
correct version. Will update.
To Andrew: Please don't pick it up. I'll refresh and send it out
again wtih all Acks.
Cyrill
prev parent reply other threads:[~2012-03-07 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 12:52 [PATCH] prctl: Use CAP_SYS_RESOUCE for PR_SET_MM option Cyrill Gorcunov
2012-03-07 17:03 ` Kees Cook
2012-03-07 20:14 ` Michael Kerrisk (man-pages)
2012-03-07 20:29 ` Paul Bolle
2012-03-07 20:33 ` Cyrill Gorcunov [this message]
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=20120307203304.GB6215@moon \
--to=gorcunov@openvz.org \
--cc=keescook@chromium.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=pebolle@tiscali.nl \
--cc=tj@kernel.org \
--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