[NFS-Ganesha-Devel] Change in ...nfs-ganesha[next]: call set_current_entry only after checking state_lock

raflopez1(a)gmail.com has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/474023 ) Change subject: call set_current_entry only after checking state_lock ...................................................................... call set_current_entry only after checking state_lock extension of d535ecf0316d8b848fabc841be9ca00a21ca9d61 - we don't want to do cleanup if state_lock_held. since put_ref is called in set_current_entry, this covers the case where data->current_obj == obj so we don't end up trying to do put_ref with cleanup before checking state_lock_held Signed-off-by: Rafael Lopez <raflopez1(a)gmail.com&gt; Change-Id: If03e53d761739380bd235fc5eb0fcfb4b14384d2 --- M src/Protocols/NFS/nfs4_op_open.c 1 file changed, 3 insertions(+), 3 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/23/474023/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/474023 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: If03e53d761739380bd235fc5eb0fcfb4b14384d2 Gerrit-Change-Number: 474023 Gerrit-PatchSet: 1 Gerrit-Owner: raflopez1(a)gmail.com Gerrit-MessageType: newchange