Description of problem: Found several memory leaks in glfs_fini to fix. 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/20553 (libgfapi: add missing unref of mgmt client in glfs_fini) posted (#1) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/20555 (rpc: add missing free of rpc->dnscache) posted (#1) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/20554 (libgfapi: fix memory leak on old volume files) posted (#2) for review on master by Zhang Huan
REVIEW: https://review.gluster.org/20573 (rpc: fix return value in rpc destroy) posted (#1) for review on master by Zhang Huan
COMMIT: https://review.gluster.org/20553 committed in master by "Amar Tumballi" <amarts> with a commit message- libgfapi: add missing unref of mgmt client in glfs_fini Change-Id: I89cdf14cb9d822eaf7c01cf0b0220b423eb5b705 fixes: bz#1607689 Signed-off-by: Zhang Huan <zhanghuan>
COMMIT: https://review.gluster.org/20554 committed in master by "Amar Tumballi" <amarts> with a commit message- libgfapi: fix memory leak on old volume files Fix missing free of fs->oldvolfile. This patch uses standard calloc/realloc to allocate memory for vol file. As by the time fs struct is destroyed, the THIS->ctx is already gone, that causes invalid memory access. Change-Id: I72ae19c76eb16e61f077714f7e52405fee721997 fixes: bz#1607689 Signed-off-by: Zhang Huan <zhanghuan>
COMMIT: https://review.gluster.org/20555 committed in master by "Amar Tumballi" <amarts> with a commit message- rpc: add missing free of rpc->dnscache Change-Id: I3fa97b99bf23459cf548205d75d2cc7936b2310e fixes: bz#1607689 Signed-off-by: Zhang Huan <zhanghuan>
COMMIT: https://review.gluster.org/20573 committed in master by "Amar Tumballi" <amarts> with a commit message- rpc: fix return value in rpc destroy Change-Id: I73a113e2d40f508fd53b273a990a2371692c87bf fixes: bz#1607689 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-5.0, please open a new bug report. glusterfs-5.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] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/