| commit | 4db72b40fdbc706f8957e9773ae73b1574b8c694 | [log] [tgz] |
|---|---|---|
| author | Jeff Layton <jlayton@redhat.com> | Tue Jan 28 13:47:46 2014 -0500 |
| committer | Trond Myklebust <trond.myklebust@primarydata.com> | Tue Jan 28 14:48:18 2014 -0500 |
| tree | 7ccf6324c0643b0b35c1ccc0895292f51000685e | |
| parent | 17dfeb9113397a6119091a491ef7182649f0c5a9 [diff] |
nfs: add memory barriers around NFS_INO_INVALID_DATA and NFS_INO_INVALIDATING If the setting of NFS_INO_INVALIDATING gets reordered to before the clearing of NFS_INO_INVALID_DATA, then another task may hit a race window where both appear to be clear, even though the inode's pages are still in need of invalidation. Fix this by adding the appropriate memory barriers. Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>