linux-next/fs/overlayfs
Miklos Szeredi f428884456 ovl: decide if revalidate needed on a per-dentry basis
Allow completely skipping ->revalidate() on a per-dentry basis, in case the
underlying layers used for a dentry do not themselves have ->revalidate().

E.g. negative overlay dentry has no underlying layers, hence revalidate is
unnecessary.  Or if lower layer is remote but overlay dentry is pure-upper,
then can skip revalidate.

The following places need to update whether the dentry needs revalidate or
not:

 - fill-super (root dentry)
 - lookup
 - create
 - fh_to_dentry

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: decide if revalidate needed on a per-dentry basis 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: decide if revalidate needed on a per-dentry basis 2020-03-17 15:04:22 +01:00
util.c ovl: decide if revalidate needed on a per-dentry basis 2020-03-17 15:04:22 +01:00