Description of problem: address a potential leak of memory in the main() of gsyncd.c Version-Release number of selected component (if applicable): mainline
REVIEW: http://review.gluster.org/14151 (geo-rep: address potential leak of memory) posted (#3) for review on master by Prasanna Kumar Kalever (pkalever)
REVIEW: http://review.gluster.org/14151 (geo-rep: address potential leak of memory) posted (#4) for review on master by Prasanna Kumar Kalever (pkalever)
COMMIT: http://review.gluster.org/14151 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit 7bf882ed1757f8b01d18d35ef869ed2cd49f1b2f Author: Prasanna Kumar Kalever <prasanna.kalever> Date: Mon May 2 19:06:47 2016 +0530 geo-rep: address potential leak of memory fix memory leak reported by clang analyzer: gsyncd.c:411:17: warning: Potential leak of memory pointed to by 'argv' in main() Change-Id: I179fb1c095cf4d331b5910df6388dc724cb4ac96 BUG: 1332419 Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever> Reviewed-on: http://review.gluster.org/14151 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat>
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-3.9.0, please open a new bug report. glusterfs-3.9.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/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/