diff options
| author | Trond Myklebust <trond.myklebust@hammerspace.com> | 2021-03-08 22:42:51 +0300 |
|---|---|---|
| committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2021-03-08 23:48:02 +0300 |
| commit | 82e7ca1334ab16e2e04fafded1cab9dfcdc11b40 (patch) | |
| tree | 828c065bd9e8576483dba415bca7e9fd7c5b9846 /fs/nfs/nfs4super.c | |
| parent | f0940f4b3284a00f38a5d42e6067c2aaa20e1f2e (diff) | |
| download | linux-82e7ca1334ab16e2e04fafded1cab9dfcdc11b40.tar.xz | |
NFS: Don't revalidate the directory permissions on a lookup failure
There should be no reason to expect the directory permissions to change
just because the directory contents changed or a negative lookup timed
out. So let's avoid doing a full call to nfs_mark_for_revalidate() in
that case.
Furthermore, if this is a negative dentry, and we haven't actually done
a new lookup, then we have no reason yet to believe the directory has
changed at all. So let's remove the gratuitous directory inode
invalidation altogether when called from
nfs_lookup_revalidate_negative().
Reported-by: Geert Jansen <gerardu@amazon.com>
Fixes: 5ceb9d7fdaaf ("NFS: Refactor nfs_lookup_revalidate()")
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'fs/nfs/nfs4super.c')
0 files changed, 0 insertions, 0 deletions