Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
NFSv4: Fix handling of non-atomic change attrbute updates
[ Upstream commit 20cf7d4 ] If the change attribute update is declared to be non-atomic by the server, or our cached value does not match the server's value before the operation was performed, then we should declare the inode cache invalid. On the other hand, if the change to the directory raced with a lookup or getattr which already updated the change attribute, then optimise away the revalidation. Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
- Loading branch information