diff options
author | Miklos Szeredi <mszeredi@redhat.com> | 2020-03-17 17:04:22 +0300 |
---|---|---|
committer | Miklos Szeredi <mszeredi@redhat.com> | 2020-03-17 17:04:22 +0300 |
commit | bccece1ead368149f90e05ad104dfbfda4422f5d (patch) | |
tree | d0d4524ba18318785ff354864f5a6aff753d59dd /fs/overlayfs/namei.c | |
parent | f428884456192230ba1573e4028fb9282ffa2bb7 (diff) | |
download | linux-bccece1ead368149f90e05ad104dfbfda4422f5d.tar.xz |
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>
Diffstat (limited to 'fs/overlayfs/namei.c')
-rw-r--r-- | fs/overlayfs/namei.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/fs/overlayfs/namei.c b/fs/overlayfs/namei.c index 76e61cc27822..0db23baf98e7 100644 --- a/fs/overlayfs/namei.c +++ b/fs/overlayfs/namei.c @@ -845,8 +845,7 @@ struct dentry *ovl_lookup(struct inode *dir, struct dentry *dentry, if (err) goto out; - if (upperdentry && (upperdentry->d_flags & DCACHE_OP_REAL || - unlikely(ovl_dentry_remote(upperdentry)))) { + if (upperdentry && upperdentry->d_flags & DCACHE_OP_REAL) { dput(upperdentry); err = -EREMOTE; goto out; |