diff options
author | Atin Mukherjee <amukherj@redhat.com> | 2017-07-05 14:58:50 +0530 |
---|---|---|
committer | Atin Mukherjee <amukherj@redhat.com> | 2017-07-06 09:46:15 +0000 |
commit | c7efdb834772ddd8f6b07214d3eb2d26425cb79b (patch) | |
tree | df2ec53d7eae9ecaaeb403139a2147a85f4f5371 /xlators/nfs | |
parent | eb96dd45f8e583c6bad84bf32ca17e2bb01dd38f (diff) |
cli/xml: fix return handling
The return code of xmlTextWriter* APIs says it returns either the bytes
written (may be 0 because of buffering) or -1 in case of error. Now if the
volume of the xml data payload is not huge then most of the time the
data to be written gets buffered, however when this grows sometimes this
APIs will return the total number of bytes written and then it becomes
absolutely mandatory that every such call is followed by
XML_RET_CHECK_AND_GOTO otherwise we may end up returning a non zero ret
code which would result into the overall xml generation to fail.
Change-Id: I02ee7076e1d8c26cf654d3dc3e77b1eb17cbdab0
BUG: 1467841
Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
Reviewed-on: https://review.gluster.org/17702
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Amar Tumballi <amarts@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Gaurav Yadav <gyadav@redhat.com>
Diffstat (limited to 'xlators/nfs')
0 files changed, 0 insertions, 0 deletions