Vivek Goyal 45aebeaf4f ovl: Ensure upper filesystem supports d_type ... In some instances xfs has been created with ftype=0 and there if a file on lower fs is removed, overlay leaves a whiteout in upper fs but that whiteout does not get filtered out and is visible to overlayfs users. And reason it does not get filtered out because upper filesystem does not report file type of whiteout as DT_CHR during iterate_dir(). So it seems to be a requirement that upper filesystem support d_type for overlayfs to work properly. Do this check during mount and fail if d_type is not supported. Suggested-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>		2016-03-21 17:31:45 +01:00
..
copy_up.c	ovl: Warn on copy up if a process has a R/O fd open to the lower file	2016-03-21 17:31:45 +01:00
dir.c	ovl: verify upper dentry before unlink and rename	2016-03-21 17:31:44 +01:00
inode.c	ovl: copy new uid/gid into overlayfs runtime inode	2016-03-03 17:17:46 +01:00
Kconfig	ovl: rename filesystem type to "overlay"	2014-11-20 16:39:59 +01:00
Makefile	ovl: rename filesystem type to "overlay"	2014-11-20 16:39:59 +01:00
overlayfs.h	ovl: Ensure upper filesystem supports d_type	2016-03-21 17:31:45 +01:00
readdir.c	ovl: Ensure upper filesystem supports d_type	2016-03-21 17:31:45 +01:00
super.c	ovl: Ensure upper filesystem supports d_type	2016-03-21 17:31:45 +01:00