Bug 764286 (GLUSTER-2554) - Invalid memory access in glusterd.
Summary: Invalid memory access in glusterd.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2554
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.1.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Gaurav
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-18 07:52 UTC by Gaurav
Modified: 2011-04-06 08:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Gaurav 2011-03-18 07:52:50 UTC
In glusterd_op_stage_set_volume, in case of key_fixed we are doing invalid access to key after memory free.

Comment 1 Vijay Bellur 2011-03-19 00:36:46 UTC
PATCH: http://patches.gluster.com/patch/6513 in master (CLI : Fix memory free for key_fixed.)

Comment 2 Vijay Bellur 2011-03-22 10:04:37 UTC
PATCH: http://patches.gluster.com/patch/6522 in release-3.1 (CLI : Fix memory free for key_fixed.)

Comment 3 M S Vishwanath Bhat 2011-04-06 05:40:47 UTC
Now glusterd is not crashing if entered wrong key. Now i get following output for the wrong key in volume set
root@tortuga:/disk1# gluster volume set hosdu dumbfdstats on
option : dumbfdstats does not exist
Did you mean dump-fd-stats?
root@tortuga:/disk1#


Note You need to log in before you can comment on or make changes to this bug.