From: Seth Forshee <seth.forshee@canonical.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-bcache@vger.kernel.org, dm-devel@redhat.com,
linux-raid@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Serge Hallyn <serge.hallyn@canonical.com>,
Andy Lutomirski <luto@amacapital.net>,
linux-kernel@vger.kernel.org,
Seth Forshee <seth.forshee@canonical.com>
Subject: [PATCH v2 0/7] User namespace mount updates
Date: Tue, 13 Oct 2015 12:04:13 -0500 [thread overview]
Message-ID: <1444755861-54997-1-git-send-email-seth.forshee@canonical.com> (raw)
Hi Eric,
Here's an update to the last round of patches for mounts in user
namespaces. The only change since last time is to split up the patch to
verify access towards block devices when mounting into several patches,
one to update lookup_bdev and one patch each for the call sites which
require updates.
Thanks,
Seth
Andy Lutomirski (1):
fs: Treat foreign mounts as nosuid
Seth Forshee (6):
block_dev: Support checking inode permissions in lookup_bdev()
block_dev: Check permissions towards block device inode when mounting
mtd: Check permissions towards mtd block device inode when mounting
selinux: Add support for unprivileged mounts from user namespaces
userns: Replace in_userns with current_in_userns
Smack: Handle labels consistently in untrusted mounts
drivers/md/bcache/super.c | 2 +-
drivers/md/dm-table.c | 2 +-
drivers/mtd/mtdsuper.c | 6 +++++-
fs/block_dev.c | 18 +++++++++++++++---
fs/exec.c | 2 +-
fs/namespace.c | 13 +++++++++++++
fs/quota/quota.c | 2 +-
include/linux/fs.h | 2 +-
include/linux/mount.h | 1 +
include/linux/user_namespace.h | 6 ++----
kernel/user_namespace.c | 6 +++---
security/commoncap.c | 4 ++--
security/selinux/hooks.c | 25 ++++++++++++++++++++++++-
security/smack/smack_lsm.c | 28 ++++++++++++++++++----------
14 files changed, 88 insertions(+), 29 deletions(-)
next reply other threads:[~2015-10-13 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 17:04 Seth Forshee [this message]
2015-10-13 17:04 ` [PATCH v2 1/7] block_dev: Support checking inode permissions in lookup_bdev() Seth Forshee
2015-10-13 17:04 ` [PATCH v2 2/7] block_dev: Check permissions towards block device inode when mounting Seth Forshee
2015-10-13 17:04 ` [PATCH v2 3/7] mtd: Check permissions towards mtd " Seth Forshee
2015-10-13 17:04 ` [PATCH v2 4/7] fs: Treat foreign mounts as nosuid Seth Forshee
2015-10-13 17:04 ` [PATCH v2 5/7] selinux: Add support for unprivileged mounts from user namespaces Seth Forshee
2015-10-13 20:27 ` Stephen Smalley
2015-10-13 17:04 ` [PATCH v2 6/7] userns: Replace in_userns with current_in_userns Seth Forshee
2015-10-13 17:04 ` [PATCH v2 7/7] Smack: Handle labels consistently in untrusted mounts Seth Forshee
2015-10-15 5:46 ` Casey Schaufler
2015-10-15 19:24 ` Seth Forshee
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=1444755861-54997-1-git-send-email-seth.forshee@canonical.com \
--to=seth.forshee@canonical.com \
--cc=dm-devel@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=selinux@tycho.nsa.gov \
--cc=serge.hallyn@canonical.com \
--cc=viro@zeniv.linux.org.uk \
/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).