Re: posix-locks memory leak?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx> 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@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux