[Gluster-devel] posix-locks memory leak?

[Basavanagowda Kanur]

Rommer,
  It is not a memory leak.
  pl_forget() is not called by protocol/server, pl_forget() is called by
__inode_destroy() after inode->ref becomes 0 (zero).

--
gowda

On Sat, Oct 18, 2008 at 8:13 PM, Rommer <rommer at active.by> wrote:

> Hello,
>
> I found memory leak in posix-locks xlator:
> pl_inode_t structure for locking allocated in functions
> truncate_stat_cbk(), pl_open_cbk() and pl_create_cbk() and
> freeing only in pl_forget() function, that never calling by
> server xlator. Server xlator does only inode_forget(), that
> does not free this structure from inode->ctx dictionary.
>
> Rommer.
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-devel/attachments/20081019/2534617d/attachment-0003.html>