Amir Goldstein b79e05aaa1 ovl: no direct iteration for dir with origin xattr ... If a non-merge dir in an overlay mount has an overlay.origin xattr, it means it was once an upper merge dir, which may contain whiteouts and then the lower dir was removed under it. Do not iterate real dir directly in this case to avoid exposing whiteouts. [SzM] Set OVL_WHITEOUT for all merge directories as well. [amir] A directory that was just copied up does not have the OVL_WHITEOUTS flag. We need to set it to fix merge dir iteration. Signed-off-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>		2017-11-09 10:23:26 +01:00
..
copy_up.c	ovl: no direct iteration for dir with origin xattr	2017-11-09 10:23:26 +01:00
dir.c	ovl: fix missing unlock_rename() in ovl_do_copy_up()	2017-10-05 15:53:18 +02:00
inode.c	ovl: no direct iteration for dir with origin xattr	2017-11-09 10:23:26 +01:00
Kconfig	ovl: introduce the inodes index dir feature	2017-07-04 22:03:17 +02:00
Makefile	ovl: split super.c	2016-12-16 11:02:56 +01:00
namei.c	ovl: do not cleanup unsupported index entries	2017-10-24 16:06:17 +02:00
overlayfs.h	ovl: no direct iteration for dir with origin xattr	2017-11-09 10:23:26 +01:00
ovl_entry.h	ovl: fix regression caused by exclusive upper/work dir protection	2017-10-05 15:53:18 +02:00
readdir.c	ovl: no direct iteration for dir with origin xattr	2017-11-09 10:23:26 +01:00
super.c	ovl: no direct iteration for dir with origin xattr	2017-11-09 10:23:26 +01:00
util.c	ovl: no direct iteration for dir with origin xattr	2017-11-09 10:23:26 +01:00