From: Seth Forshee <seth.forshee@canonical.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: "Serge E. Hallyn" <serge.hallyn@ubuntu.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Seth Forshee <seth.forshee@canonical.com>
Subject: [PATCH 1/2] fs: Allow bind mounts with locked children on permaenetly empty directories
Date: Wed, 9 Mar 2016 09:18:06 -0600 [thread overview]
Message-ID: <1457536687-32794-2-git-send-email-seth.forshee@canonical.com> (raw)
In-Reply-To: <1457536687-32794-1-git-send-email-seth.forshee@canonical.com>
Forbidding a bind mount due to a locked child on a permanently
empty directory provides no security benefit since the
directory cannot contain any contents which have been overmounted
for security reasons.
Cc: stable@vger.kernel.org # v4.1+
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
---
fs/namespace.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/namespace.c b/fs/namespace.c
index 4fb1691b4355..930f5557b1d1 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -2065,6 +2065,8 @@ static bool has_locked_children(struct mount *mnt, struct dentry *dentry)
list_for_each_entry(child, &mnt->mnt_mounts, mnt_child) {
if (!is_subdir(child->mnt_mountpoint, dentry))
continue;
+ if (is_empty_dir_inode(child->mnt_mountpoint->d_inode))
+ continue;
if (child->mnt.mnt_flags & MNT_LOCKED)
return true;
--
1.9.1
next prev parent reply other threads:[~2016-03-09 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 15:18 [PATCH 0/2] Fix debugfs bind mount regression Seth Forshee
2016-03-09 15:18 ` Seth Forshee [this message]
2016-03-09 20:32 ` [PATCH 1/2] fs: Allow bind mounts with locked children on permaenetly empty directories Serge E. Hallyn
2016-03-09 15:18 ` [PATCH 2/2] debugfs: Make automount point inodes permanently empty Seth Forshee
2016-03-09 20:32 ` Serge E. Hallyn
2016-03-09 20:57 ` [PATCH 0/2] Fix debugfs bind mount regression Eric W. Biederman
2016-03-09 21:18 ` Serge Hallyn
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=1457536687-32794-2-git-send-email-seth.forshee@canonical.com \
--to=seth.forshee@canonical.com \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge.hallyn@ubuntu.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
all inboxes | Powered by JetHome®