Bug 765553 (GLUSTER-3821)

Summary:	call cli_cmd_unlock in the same function as cli_cmd_lock
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	cli	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	pre-release	CC:	gluster-bugs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Niels de Vos 2011-11-21 10:17:41 UTC

cli_cmd_submit calls cli_cmd_lock, but cli_cmd_unlock is done in
cli_cmd_await_response. It is clearer to do the locking and unlocking in
the same function.

Only cli_cmd_submit seems to call cli_cmd_await_response, therefore
moving the cli_cmd_unlock to cli_cmd_submit should be safe.

Vijay Bellur requested to open a bug: http://review.gluster.com/721

Comment 1 Anand Avati 2011-11-23 09:06:32 UTC

CHANGE: http://review.gluster.com/721 (cli_cmd_submit calls cli_cmd_lock, but cli_cmd_unlock is done in) merged in master by Vijay Bellur (vijay)