[NFS-Ganesha-Devel] Change in ...nfs-ganesha[next]: Repopulate chunk after reacquiring a dropped lock

madhu.punjabi(a)in.ibm.com has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/440079 Change subject: Repopulate chunk after reacquiring a dropped lock ...................................................................... Repopulate chunk after reacquiring a dropped lock In mdcache_readdir_chunked() when first_pass=false, it means we have a valid chunk. But in the next pass if write lock has not been already acquired then we drop the existing lock and acquire a write lock. Here after dropping the lock there is a possibility that another thread may acquire the lock and discard the chunk. Thus, we not cannot trust the chunk pointer and we should repopulate the chunk. Change-Id: I41c806b96e6cd26789693bf5cfdb070675f0ffac Signed-off-by: Madhu Thorat <madhu.punjabi(a)in.ibm.com&gt; --- M src/FSAL/Stackable_FSALs/FSAL_MDCACHE/mdcache_helpers.c 1 file changed, 18 insertions(+), 1 deletion(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/79/440079/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/440079 To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I41c806b96e6cd26789693bf5cfdb070675f0ffac Gerrit-Change-Number: 440079 Gerrit-PatchSet: 1 Gerrit-Owner: madhu.punjabi(a)in.ibm.com Gerrit-MessageType: newchange