From: Kees Cook <keescook@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <cl@linux.com>,
Andy Lutomirski <luto@amacapital.net>,
James Morris <jmorris@namei.org>,
Andy Lutomirski <luto@kernel.org>,
Andrew Morton <akpm@linuxfoundation.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
James Morris <james.l.morris@oracle.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Ted Ts'o <tytso@mit.edu>, "Andrew G. Morgan" <morgan@kernel.org>,
Linux API <linux-api@vger.kernel.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Austin S Hemmelgarn <ahferroin7@gmail.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
Aaron Jones <aaronmdjones@gmail.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
LKML <linux-kernel@vger.kernel.org>,
Markku Savela <msa@moth.iki.fi>, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v4 1/2] capabilities: Ambient capabilities
Date: Fri, 17 Jul 2015 16:10:09 -0700 [thread overview]
Message-ID: <CAGXu5j+V0fMae5OOHwU5DcMrG0TCANYOTfbz5+LDZZqYKcXAaw@mail.gmail.com> (raw)
In-Reply-To: <20150717135057.8e09390f1c10bc11d10a42f5@linux-foundation.org>
On Fri, Jul 17, 2015 at 1:50 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Fri, 17 Jul 2015 15:40:57 -0500 (CDT) Christoph Lameter <cl@linux.com> wrote:
>
>> Here is a test program that can be used to verify the functionality.
>
> I slurped that into the changelog.
>
> Adding a selftest into tools/testing/selftests/ would be appropriate.
Yes please! I'd love to see a general privilege transition testing
area. But starting with just this would be fine. :)
-Kees
--
Kees Cook
Chrome OS Security
next prev parent reply other threads:[~2015-07-17 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 19:46 [PATCH v4 0/2] capabilities: Ambient capability patchset Andy Lutomirski
2015-07-14 19:46 ` [PATCH v4 1/2] capabilities: Ambient capabilities Andy Lutomirski
[not found] ` <9f660ee708e58892bfa7012b6b9c840298e24544.1436903028.git.luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-07-15 11:13 ` James Morris
[not found] ` <alpine.LRH.2.11.1507152033420.8351-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
2015-07-15 17:09 ` Andy Lutomirski
[not found] ` <CALCETrWMBZ0p7P1FvtrYp5ChJXvvRzy0JpjS8KwUUa5m9gqgQA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-17 20:40 ` Christoph Lameter
[not found] ` <alpine.DEB.2.11.1507171539590.13763-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-07-17 20:50 ` Andrew Morton
2015-07-17 23:10 ` Kees Cook [this message]
[not found] ` <CAGXu5j+V0fMae5OOHwU5DcMrG0TCANYOTfbz5+LDZZqYKcXAaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-17 23:21 ` Andy Lutomirski
2015-07-14 19:46 ` [PATCH v4 2/2] capabilities: Add a securebit to disable PR_CAP_AMBIENT_RAISE Andy Lutomirski
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=CAGXu5j+V0fMae5OOHwU5DcMrG0TCANYOTfbz5+LDZZqYKcXAaw@mail.gmail.com \
--to=keescook@chromium.org \
--cc=aaronmdjones@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=james.l.morris@oracle.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=morgan@kernel.org \
--cc=msa@moth.iki.fi \
--cc=mtk.manpages@gmail.com \
--cc=serge.hallyn@canonical.com \
--cc=serge.hallyn@ubuntu.com \
--cc=serge@hallyn.com \
--cc=tytso@mit.edu \
--cc=zohar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).