Commit 82e7ca1
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: 5ceb9d7 ("NFS: Refactor nfs_lookup_revalidate()")
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>1 parent f0940f4 commit 82e7ca1
1 file changed
Lines changed: 17 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1401 | 1401 | | |
1402 | 1402 | | |
1403 | 1403 | | |
| 1404 | + | |
| 1405 | + | |
| 1406 | + | |
| 1407 | + | |
| 1408 | + | |
| 1409 | + | |
| 1410 | + | |
| 1411 | + | |
| 1412 | + | |
1404 | 1413 | | |
1405 | 1414 | | |
1406 | 1415 | | |
| |||
1435 | 1444 | | |
1436 | 1445 | | |
1437 | 1446 | | |
1438 | | - | |
1439 | 1447 | | |
1440 | 1448 | | |
1441 | 1449 | | |
| |||
1525 | 1533 | | |
1526 | 1534 | | |
1527 | 1535 | | |
| 1536 | + | |
| 1537 | + | |
| 1538 | + | |
| 1539 | + | |
| 1540 | + | |
| 1541 | + | |
| 1542 | + | |
1528 | 1543 | | |
1529 | 1544 | | |
1530 | 1545 | | |
| |||
1567 | 1582 | | |
1568 | 1583 | | |
1569 | 1584 | | |
1570 | | - | |
| 1585 | + | |
1571 | 1586 | | |
1572 | 1587 | | |
1573 | 1588 | | |
| |||
2064 | 2079 | | |
2065 | 2080 | | |
2066 | 2081 | | |
2067 | | - | |
2068 | 2082 | | |
2069 | 2083 | | |
2070 | 2084 | | |
| |||
0 commit comments