Bug 1079215 - memory needs to freed when dict_set fails
Summary: memory needs to freed when dict_set fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-21 08:55 UTC by Pranith Kumar K
Modified: 2014-11-11 08:29 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of:
Environment:
Last Closed: 2014-11-11 08:29:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Pranith Kumar K 2014-03-21 08:55:40 UTC 
Description of problem:
in dict_set_* operations if dict_set fails, memory for the value is not freed. Found the bug while browsing the code. Very difficult to hit this issue.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Anand Avati 2014-03-21 08:57:20 UTC 
REVIEW: http://review.gluster.org/7310 (dict: de-allocate data on dict-set failures) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu)
Comment 2 Anand Avati 2014-04-29 01:00:51 UTC 
COMMIT: http://review.gluster.org/7310 committed in master by Anand Avati (avati) 
------
commit 3ea85192f1521c32915ed38bb4db61be11d59922
Author: Pranith Kumar K <pkarampu>
Date:   Fri Mar 21 08:35:12 2014 +0530

    dict: de-allocate data on dict-set failures
    
    Found the bug while browsing code. Very difficult to hit this though.
    
    Change-Id: I84bd5d23d19b6aa16866fc0f1b56aa22cb8a5f1f
    BUG: 1079215
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/7310
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Anand Avati <avati>
Comment 3 Niels de Vos 2014-09-22 12:37:05 UTC 
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/
Comment 4 Niels de Vos 2014-11-11 08:29:04 UTC 
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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users
Note You need to log in before you can comment on or make changes to this bug.