Gluster users - Jan 2016 - [Gluster-devel] Memory leak in GlusterFS FUSE client

I see extra GF_FREE (node); added with two patches:

==$ git diff HEAD~2 | gist
https://gist.github.com/9524fa2054cc48278ea8
==
Is that intentionally? I guess I face double-free issue.

On ??????, 21 ????? 2016 ?. 17:29:53 EET Kaleb KEITHLEY
wrote:
> On 01/20/2016 04:08 AM, Oleksandr Natalenko wrote:
> > Yes, there are couple of messages like this in my logs too (I guess
one
> > message per each remount):
> > 
> > ==> > [2016-01-18 23:42:08.742447] I
[fuse-bridge.c:3875:notify_kernel_loop] 0-
> > glusterfs-fuse: kernel notifier loop terminated
> > ==> 
> Bug reports and fixes for master and release-3.7 branches are:
> 
> master)
>  https://bugzilla.redhat.com/show_bug.cgi?id=1288857
>  http://review.gluster.org/12886
> 
> release-3.7)
>  https://bugzilla.redhat.com/show_bug.cgi?id=1288922
>  http://review.gluster.org/12887
> 
> The release-3.7 fix will be in glusterfs-3.7.7 when it's released.
> 
> I think with even with the above fixes applied there are still some
> issues remaining. I have submitted additional/revised fixes on top of
> the above fixes at:
> 
>  master: http://review.gluster.org/13274
>  release-3.7: http://review.gluster.org/13275
> 
> I invite you to review the patches in gerrit (review.gluster.org).
> 
> Regards,
> 
> --
> 
> Kaleb

On 01/21/2016 06:59 PM, Oleksandr Natalenko wrote:
> I see extra GF_FREE (node); added with two patches:
> 
> ==> $ git diff HEAD~2 | gist
> https://gist.github.com/9524fa2054cc48278ea8
> ==> 
> Is that intentionally? I guess I face double-free issue.
> 
I presume you're referring to the release-3.7 branch.

Yup, bad edit. Long day. That's why we review. ;-)

Please try the latest.

Thanks,

--

Kaleb