>From Malahal <mala...@gmail.com>:

Malahal has uploaded this change for review. ( 
https://review.gerrithub.io/369489


Change subject: Fix HASHTABLE_ERROR_KEY_ALREADY_EXISTS error
......................................................................

Fix HASHTABLE_ERROR_KEY_ALREADY_EXISTS error

commit feb12d2fe13fcdbd5ae80cbe6575af98c4657520 introduced a new
paradigm where get_nlm_client() calls hashtable_getlatch() followed by
hashtable_deletelatched() and then hashtable_setlatched() call sequence
if the entry's refcount is zero. In this case latch->locator will be set
by hashtable_getlatch, and hashtable_setlatched thinks we are inserting
an existing record. Let hashtable_deletelatched set latch->locator to
NULL to avoid false positive return of KEY_ALREADY_EXISTS error.

Change-Id: I8f971dd197452b7a5d33b97990b463acda2431dc
Signed-off-by: Malahal Naineni <mala...@us.ibm.com>
---
M src/hashtable/hashtable.c
1 file changed, 7 insertions(+), 4 deletions(-)



  git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha 
refs/changes/89/369489/1
-- 
To view, visit https://review.gerrithub.io/369489
To unsubscribe, visit https://review.gerrithub.io/settings

Gerrit-Project: ffilz/nfs-ganesha
Gerrit-Branch: next
Gerrit-MessageType: newchange
Gerrit-Change-Id: I8f971dd197452b7a5d33b97990b463acda2431dc
Gerrit-Change-Number: 369489
Gerrit-PatchSet: 1
Gerrit-Owner: Malahal <mala...@gmail.com>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Reply via email to