+++ This bug was initially created as a clone of Bug #1589691 +++ Description of problem: On code-reading found that there is a leak in this function that needs to be fixed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Worker Ant on 2018-06-11 04:19:39 EDT --- REVIEW: https://review.gluster.org/20211 (protocol/server: Fix xdata leak in seek fop) posted (#1) for review on master by Pranith Kumar Karampuri --- Additional comment from Worker Ant on 2018-06-11 08:51:19 EDT --- COMMIT: https://review.gluster.org/20211 committed in master by "Raghavendra G" <rgowdapp> with a commit message- protocol/server: Fix xdata leak in seek fop Change-Id: I6125283ed22c04564f0b77bb7a50579a83e02eb0 fixes: bz#1589691 Signed-off-by: Pranith Kumar K <pkarampu>
COMMIT: https://review.gluster.org/20230 committed in release-4.1 by "Pranith Kumar Karampuri" <pkarampu> with a commit message- protocol/server: Fix xdata leak in seek fop Change-Id: I6125283ed22c04564f0b77bb7a50579a83e02eb0 fixes: bz#1590128 Signed-off-by: Pranith Kumar K <pkarampu> (cherry picked from commit fd5b48ea0afd907deb08604415bee14ab65f378b)
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/