There is a memleak in release-3.1 glusterd. Ran volume set in a loop and valgrind reported the leak.



8,910 bytes in 135 blocks are definitely lost in loss record 110 of 118
==6916==    at 0x4C277CC: calloc (vg_replace_malloc.c:467)
==6916==    by 0x4E79AE4: __gf_calloc (mem-pool.c:142)
==6916==    by 0x74D7789: gf_strdup (mem-pool.h:91)
==6916==    by 0x74D8CA3: option_complete (glusterd-volgen.c:741)
==6916==    by 0x74D8D49: glusterd_check_globaloption (glusterd-volgen.c:762)
==6916==    by 0x74BAAE2: glusterd_op_set_volume (glusterd-op-sm.c:3993)
==6916==    by 0x74BF9E5: glusterd_op_commit_perform (glusterd-op-sm.c:5642)
==6916==    by 0x74BDF72: glusterd_op_ac_send_commit_op (glusterd-op-sm.c:5042)
==6916==    by 0x74BFE91: glusterd_op_sm (glusterd-op-sm.c:5916)
==6916==    by 0x74A5698: glusterd_handle_set_volume (glusterd-handler.c:1779)
==6916==    by 0x50A993B: rpcsvc_handle_rpc_call (rpcsvc.c:998)
==6916==    by 0x50A9CDE: rpcsvc_notify (rpcsvc.c:1094)