Description of problem: Found several issues during testing gluster client, in both rpc-clnt and socket. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/18984 (protocol/client: fix an issue when a request fails to send) posted (#1) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/18986 (rpc: simplify parameters when a saved frame is forced to unwind) posted (#1) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/18985 (rpc: fix incorrect return value when xdr decode fails) posted (#1) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/18987 (rpc-transport/socket: reconfigure fails if socket is not valid) posted (#1) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/19100 (rpc: fix crash on submiting requests when brick is down) posted (#1) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/18985 (rpc: fix incorrect return value when xdr decode fails) posted (#3) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/18986 (rpc: simplify parameters when a saved frame is forced to unwind) posted (#3) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/18984 (protocol/client: fix an issue when a request fails to send) posted (#3) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/18987 (rpc-transport/socket: reconfigure fails if socket is not valid) posted (#3) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/19100 (rpc: fix crash on submiting requests when brick is down) posted (#2) for review on master by Amar Tumballi
COMMIT: https://review.gluster.org/18985 committed in master by "Amar Tumballi" <amarts> with a commit message- rpc: fix incorrect return value when xdr decode fails xdr_replymsg is called to decode reply message, and it returns failure if the message is corrupted. However, retrieving return value from the global errno is 0 even xdr_replymsg fails. Fix this issue by simply returning a negative value if call to xdr_replymsg fails. Change-Id: I2b9a1dc97652fbb6cf6568ea617f120713784a55 BUG: 1523122 Signed-off-by: Zhang Huan <zhanghuan>
COMMIT: https://review.gluster.org/18986 committed in master by "Amar Tumballi" <amarts> with a commit message- rpc: simplify parameters when a saved frame is forced to unwind When a saved frame is to be forced unwind, there is no need to pass an empty iovector without any data pointed to. Change-Id: I6e858fb38644326e22239b83272b15db656035e5 BUG: 1523122 Signed-off-by: Zhang Huan <zhanghuan>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report. glusterfs-v4.1.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/