linux/fs/overlayfs
Miklos Szeredi bccece1ead ovl: allow remote upper
No reason to prevent upper layer being a remote filesystem.  Do the
revalidation in that case, just as we already do for lower layers.

This lets virtiofs be used as upper layer, which appears to be a real use
case.

Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
2020-03-17 15:04:22 +01:00
..
copy_up.c ovl: ignore failure to copy up unknown xattrs 2020-03-17 15:04:22 +01:00
dir.c ovl: decide if revalidate needed on a per-dentry basis 2020-03-17 15:04:22 +01:00
export.c ovl: decide if revalidate needed on a per-dentry basis 2020-03-17 15:04:22 +01:00
file.c ovl: fix lockdep warning for async write 2020-03-13 15:53:06 +01:00
inode.c ovl: simplify i_ino initialization 2020-03-17 15:04:22 +01:00
Kconfig ovl: fix some xino configurations 2020-03-13 15:53:06 +01:00
Makefile treewide: Add SPDX license identifier - Makefile/Kconfig 2019-05-21 10:50:46 +02:00
namei.c ovl: allow remote upper 2020-03-17 15:04:22 +01:00
overlayfs.h ovl: decide if revalidate needed on a per-dentry basis 2020-03-17 15:04:22 +01:00
ovl_entry.h ovl: layer is const 2020-01-24 09:46:45 +01:00
readdir.c ovl: layer is const 2020-01-24 09:46:45 +01:00
super.c ovl: allow remote upper 2020-03-17 15:04:22 +01:00
util.c ovl: allow remote upper 2020-03-17 15:04:22 +01:00