Miklos Szeredi 69c433ed2e fs: limit filesystem stacking depth ... 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>		2014-10-24 00:14:39 +02:00
..
crypto.c	tree-wide: use reinit_completion instead of INIT_COMPLETION	2013-11-15 09:32:21 +09:00
debug.c
dentry.c	ecryptfs: ->lower_path.dentry is never NULL	2013-10-24 23:34:48 -04:00
ecryptfs_kernel.h	ecryptfs: get rid of ecryptfs_set_dentry_lower{,_mnt}	2013-10-24 23:34:48 -04:00
file.c	Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs	2014-10-13 11:28:42 +02:00
inode.c	Minor code cleanups and a fix for when eCryptfs metadata is stored in xattrs	2014-10-11 08:01:27 -04:00
Kconfig
keystore.c	ecryptfs: remove unnecessary break after goto	2014-07-14 14:29:11 -05:00
kthread.c
main.c	fs: limit filesystem stacking depth	2014-10-24 00:14:39 +02:00
Makefile
messaging.c	fs/ecryptfs/messaging.c: remove null test before kfree	2014-07-03 16:38:09 -05:00
miscdev.c
mmap.c
read_write.c	ecryptfs: don't open-code kernel_read()	2013-05-09 13:39:58 -04:00
super.c	mm + fs: store shadow entries in page cache	2014-04-03 16:21:01 -07:00