From: ebiederm@xmission.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Seth Forshee <seth.forshee@canonical.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org, linux-security-module@vger.kernel.org,
Kees Cook <keescook@chromium.org>,
Andreas Gruenbacher <agruenba@redhat.com>,
Andy Lutomirski <luto@kernel.org>,
"Andrew G. Morgan" <morgan@kernel.org>
Subject: Re: [PATCH v2] Introduce v3 namespaced file capabilities
Date: Sat, 29 Apr 2017 13:22:52 -0500 [thread overview]
Message-ID: <87a86zul8j.fsf@xmission.com> (raw)
In-Reply-To: <20170429041534.GA25594@mail.hallyn.com> (Serge E. Hallyn's message of "Fri, 28 Apr 2017 23:15:34 -0500")
"Serge E. Hallyn" <serge@hallyn.com> writes:
[snip]
> A patch to linux-test-project adding a new set of tests for this
> functionality is in the nsfscaps branch at github.com/hallyn/ltp
>
> Changelog:
> Nov 02 2016: fix invalid check at refuse_fcap_overwrite()
> Nov 07 2016: convert rootid from and to fs user_ns
> (From ebiederm: mar 28 2017)
> commoncap.c: fix typos - s/v4/v3
> get_vfs_caps_from_disk: clarify the fs_ns root access check
> nsfscaps: change the code split for cap_inode_setxattr()
> Apr 09 2017:
> don't return v3 cap for caps owned by current root.
> return a v2 cap for a true v2 cap in non-init ns
> Apr 18 2017:
> . Change the flow of fscap writing to support s_user_ns writing.
> . Remove refuse_fcap_overwrite(). The value of the previous
> xattr doesn't matter.
> Apr 24 2017:
> . incorporate Eric's incremental diff
> . move cap_convert_nscap to setxattr and simplify its usage
> ---
> fs/xattr.c | 6 +
> include/linux/capability.h | 3 +-
> include/linux/security.h | 2 +
> include/uapi/linux/capability.h | 22 +++-
> security/commoncap.c | 269 +++++++++++++++++++++++++++++++++++++---
> 5 files changed, 279 insertions(+), 23 deletions(-)
>
Grrr. No Signed-off-by: again.
Eric
prev parent reply other threads:[~2017-04-29 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 4:15 [PATCH v2] Introduce v3 namespaced file capabilities Serge E. Hallyn
2017-04-29 18:22 ` Eric W. Biederman [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=87a86zul8j.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=agruenba@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@kernel.org \
--cc=morgan@kernel.org \
--cc=serge@hallyn.com \
--cc=seth.forshee@canonical.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