[Gluster-devel] [Gluster-users] GlusterFS v3.7.8 client leaks summary — part II

[Soumya Koduri]

On 02/16/2016 08:06 PM, Oleksandr Natalenko wrote:
> Hmm, OK. I've rechecked 3.7.8 with the following patches (latest
> revisions):
>
> ===
> Soumya Koduri (3):
>        gfapi: Use inode_forget in case of handle objects
>        inode: Retire the inodes from the lru list in inode_table_destroy
>        rpc: Fix for rpc_transport_t leak
> ===
>
> Here is Valgrind output: [1]
>
> It seems that all leaks are gone, and that is very nice.

At least major chunk of leaks seem to have gone. Many thanks to you too 
for very detailed tests and analysis :)

-Soumya

>
> Many thanks to all devs.
>
> [1] https://gist.github.com/anonymous/eddfdaf3eb7bff458326
>
> 16.02.2016 15:30, Soumya Koduri wrote:
>> I have tested using your API app (I/Os done - create,write and stat).
>> I still do not see any inode related leaks. However I posted another
>> fix for rpc_transport object related leak [1].
>>
>> I request you to re-check if you have the latest patch of [2] applied
>> in your build.
>>
>> [1] http://review.gluster.org/#/c/13456/
>> [2] http://review.gluster.org/#/c/13125/