linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	hch@infradead.org, akpm@linux-foundation.org, apw@canonical.com,
	nbd@openwrt.org, neilb@suse.de, jordipujolp@gmail.com,
	ezk@fsl.cs.sunysb.edu, dhowells@redhat.com,
	sedat.dilek@gmail.com, hooanon05@yahoo.co.jp, mszeredi@suse.cz
Subject: [PATCH 12/13] fs: limit filesystem stacking depth
Date: Fri, 23 May 2014 11:43:42 +0200	[thread overview]
Message-ID: <1400838223-30844-13-git-send-email-miklos@szeredi.hu> (raw)
In-Reply-To: <1400838223-30844-1-git-send-email-miklos@szeredi.hu>

From: Miklos Szeredi <mszeredi@suse.cz>

Add a simple read-only counter to super_block that indicates how deep this
is in the stack of filesystems.  Previously ecryptfs was the only stackable
filesystem and it explicitly disallowed multiple layers of itself.

Overlayfs, however, can be stacked recursively and also may be stacked
on top of ecryptfs or vice versa.

To limit the kernel stack usage we must limit the depth of the
filesystem stack.  Initially the limit is set to 2.

Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
---
 fs/ecryptfs/main.c   |  7 +++++++
 fs/overlayfs/super.c | 10 ++++++++++
 include/linux/fs.h   | 11 +++++++++++
 3 files changed, 28 insertions(+)

diff --git a/fs/ecryptfs/main.c b/fs/ecryptfs/main.c
index 1b119d3bf924..c4cd1fd86cc2 100644
--- a/fs/ecryptfs/main.c
+++ b/fs/ecryptfs/main.c
@@ -566,6 +566,13 @@ static struct dentry *ecryptfs_mount(struct file_system_type *fs_type, int flags
 	s->s_maxbytes = path.dentry->d_sb->s_maxbytes;
 	s->s_blocksize = path.dentry->d_sb->s_blocksize;
 	s->s_magic = ECRYPTFS_SUPER_MAGIC;
+	s->s_stack_depth = path.dentry->d_sb->s_stack_depth + 1;
+
+	rc = -EINVAL;
+	if (s->s_stack_depth > FILESYSTEM_MAX_STACK_DEPTH) {
+		pr_err("eCryptfs: maximum fs stacking depth exceeded\n");
+		goto out_free;
+	}
 
 	inode = ecryptfs_get_inode(path.dentry->d_inode, s);
 	rc = PTR_ERR(inode);
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index fcbd92a14e69..04879abbbf98 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -644,6 +644,16 @@ static int ovl_fill_super(struct super_block *sb, void *data, int silent)
 	}
 	ufs->lower_namelen = statfs.f_namelen;
 
+	sb->s_stack_depth = max(upperpath.mnt->mnt_sb->s_stack_depth,
+				lowerpath.mnt->mnt_sb->s_stack_depth) + 1;
+
+	err = -EINVAL;
+	if (sb->s_stack_depth > FILESYSTEM_MAX_STACK_DEPTH) {
+		pr_err("overlayfs: maximum fs stacking depth exceeded\n");
+		goto out_put_lowerpath;
+	}
+
+
 	ufs->upper_mnt = clone_private_mount(&upperpath);
 	err = PTR_ERR(ufs->upper_mnt);
 	if (IS_ERR(ufs->upper_mnt)) {
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 48d3bd908b5d..340c5e3be0d0 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -266,6 +266,12 @@ struct iattr {
  */
 #include <linux/quota.h>
 
+/*
+ * Maximum number of layers of fs stack.  Needs to be limited to
+ * prevent kernel stack overflow
+ */
+#define FILESYSTEM_MAX_STACK_DEPTH 2
+
 /** 
  * enum positive_aop_returns - aop return codes with specific semantics
  *
@@ -1269,6 +1275,11 @@ struct super_block {
 	struct list_lru		s_dentry_lru ____cacheline_aligned_in_smp;
 	struct list_lru		s_inode_lru ____cacheline_aligned_in_smp;
 	struct rcu_head		rcu;
+
+	/*
+	 * Indicates how deep in a filesystem stack this SB is
+	 */
+	int s_stack_depth;
 };
 
 extern struct timespec current_fs_time(struct super_block *sb);
-- 
1.8.1.4


  parent reply	other threads:[~2014-05-23  9:44 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  9:43 [PATCH 00/13] overlay filesystem v22 Miklos Szeredi
2014-05-23  9:43 ` [PATCH 01/13] vfs: add i_op->dentry_open() Miklos Szeredi
2014-05-23  9:43 ` [PATCH 02/13] vfs: export do_splice_direct() to modules Miklos Szeredi
2014-05-23  9:43 ` [PATCH 03/13] vfs: export __inode_permission() " Miklos Szeredi
2014-05-23  9:43 ` [PATCH 04/13] vfs: introduce clone_private_mount() Miklos Szeredi
2014-05-23  9:43 ` [PATCH 05/13] vfs: export check_sticky() Miklos Szeredi
2014-05-23  9:43 ` [PATCH 06/13] vfs: add whiteout support Miklos Szeredi
2014-05-24  8:29   ` Tetsuo Handa
2014-05-23  9:43 ` [PATCH 07/13] vfs: add RENAME_WHITEOUT Miklos Szeredi
2014-05-24  8:02   ` Azat Khuzhin
2014-05-23  9:43 ` [PATCH 08/13] overlay filesystem Miklos Szeredi
2014-05-23  9:43 ` [PATCH 09/13] overlayfs: add statfs support Miklos Szeredi
2014-05-23  9:43 ` [PATCH 10/13] overlayfs: implement show_options Miklos Szeredi
2014-05-23  9:43 ` [PATCH 11/13] overlay: overlay filesystem documentation Miklos Szeredi
2014-05-23  9:43 ` Miklos Szeredi [this message]
2014-05-23  9:43 ` [PATCH 13/13] vfs: dcache: Export d_ancestor to modules Miklos Szeredi
2014-05-26  1:56 ` [PATCH 00/13] overlay filesystem v22 J. R. Okajima
2014-05-28 16:06   ` Miklos Szeredi
2014-05-29 10:26   ` David Howells
2014-05-29 11:26     ` Miklos Szeredi
2014-05-29 10:54 ` Kernel errors with " David Howells
2014-05-29 11:16 ` David Howells
2014-05-29 11:28 ` David Howells
2014-05-29 12:07   ` Miklos Szeredi
2014-05-29 16:06     ` Miklos Szeredi
2014-05-29 16:10       ` Sedat Dilek
2014-05-29 16:23     ` More kernel " David Howells
2014-05-29 16:36       ` Miklos Szeredi
2014-05-29 16:44       ` David Howells
2014-05-29 16:48 ` Unionmount and overlayfs testsuite David Howells
2014-05-29 17:11   ` Sedat Dilek
2014-05-29 17:15   ` David Howells
2014-05-29 17:19     ` Sedat Dilek
2014-05-29 17:24     ` David Howells
2014-05-29 17:36       ` Sedat Dilek
2014-05-29 17:41       ` David Howells
2014-05-29 17:44         ` Sedat Dilek
2014-05-29 18:22         ` David Howells
2014-05-29 18:44           ` Sedat Dilek
2014-05-29 18:53             ` Sedat Dilek
2014-05-29 19:20             ` David Howells
2014-05-29 19:24               ` Sedat Dilek
2014-05-29 19:25           ` David Howells
2014-05-29 19:28             ` Sedat Dilek
2014-05-29 19:35           ` David Howells
2014-05-29 20:00             ` Sedat Dilek
2014-05-29 20:59             ` David Howells
2014-05-30  4:15               ` Sedat Dilek
2014-05-30  4:29                 ` Sedat Dilek
2014-05-30  7:54               ` David Howells
2014-05-29 17:35     ` Sedat Dilek
2014-05-29 17:50     ` David Howells
2014-05-29 17:58       ` Sedat Dilek
2014-05-29 18:23       ` Dave Jones
2014-05-29 18:27       ` David Howells
2014-05-29 17:17   ` David Howells
2014-05-29 23:21   ` Dave Chinner
2014-05-30  3:35   ` J. R. Okajima
2014-05-30  4:44     ` J. R. Okajima
2014-05-30  8:49   ` David Howells
2014-05-30  9:15     ` J. R. Okajima
2014-06-03  8:08     ` Sedat Dilek
2014-06-03  9:00     ` David Howells
2014-06-03  9:12       ` Miklos Szeredi
2014-06-03  9:18       ` Sedat Dilek
2014-06-03  9:26         ` Sedat Dilek
2014-06-03  9:39           ` Sedat Dilek
2014-06-03  9:42           ` Miklos Szeredi
2014-06-03 10:15             ` Sedat Dilek
2014-06-03 10:21             ` Sedat Dilek
2014-06-03 10:55               ` Sedat Dilek
2014-06-03 10:33           ` David Howells
2014-06-03 13:21             ` Miklos Szeredi
2014-06-03 14:26               ` Sedat Dilek
2014-06-03 15:30             ` David Howells
2014-06-03 15:53               ` Miklos Szeredi
2014-06-05 22:16               ` David Howells
2014-06-24 16:46               ` Overlayfs rename bug David Howells
2014-07-08  9:29                 ` Miklos Szeredi
2014-07-08  9:56                 ` David Howells
2014-07-09 14:14                   ` Miklos Szeredi
2014-05-30  9:14   ` Unionmount and overlayfs testsuite David Howells
2014-05-29 17:29 ` Kernel errors with overlay filesystem v22 David Howells

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=1400838223-30844-13-git-send-email-miklos@szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=dhowells@redhat.com \
    --cc=ezk@fsl.cs.sunysb.edu \
    --cc=hch@infradead.org \
    --cc=hooanon05@yahoo.co.jp \
    --cc=jordipujolp@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@suse.cz \
    --cc=nbd@openwrt.org \
    --cc=neilb@suse.de \
    --cc=sedat.dilek@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --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).