{"push_id":964361388,"size":5,"distinct_size":5,"ref":"refs/heads/memleak-3.7.7","head":"68168cabae7c2182e419f563a4d56c57b4531609","before":"9c5d9d8392456611fc26eb82e029c57ef3898e88","commits":[{"sha":"0cedc3d97fb4057afdd9b464e507705da797cac8","author":{"email":"d83894965d597d87a548ff845500589a4a6a54e9@redhat.com","name":"Soumya Koduri"},"message":"gfapi: Fix inode nlookup counts\n\nAs inode_lookup() is done to keep the inodes in the lru list\nto speed up the further lookups, for gfapi it makes sense to\ndo the lookup only when the application is performing any fops\non that inode and forget it once it is done with it.\n\nHence, as all the fops in gfapi are either done using fd or handle,\nhave made changes to take a lookup referene during -\n    * glfs_fd_bind\n    * glfs_create_handle\nand release this reference ('inode_forget') during -\n    * glfs_fd_destroy\n    * glfs_h_close\n\nChange-Id: Id2c7ab178894a10c0030c143ba71e7813df8d18c\nSigned-off-by: Soumya Koduri <skoduri@redhat.com>\nBUG: 1295107","distinct":true,"url":"https://api.github.com/repos/pfactum/glusterfs/commits/0cedc3d97fb4057afdd9b464e507705da797cac8"},{"sha":"47081c6690a8699e9efee45f6e7e609c5219f830","author":{"email":"d83894965d597d87a548ff845500589a4a6a54e9@redhat.com","name":"Soumya Koduri"},"message":"inode: Retire the inodes from the lru list in inode_table_destroy\n\nInodes from the lru list are not moved to purge list unless they\nare retired. Also process the lru list first to unset their parent\nas we need to unset their dentry entries (the ones which may not be\nunset during '__inode_passivate' as they were hashed) which in turn\nshall unref their parent inodes which could be in active list.\n\nThese parent inodes when unref'ed may well again fall into lru list\nand if we are at the end of traversing the list, we may miss to\ndelete/retire that entry. Hence traverse the lru list till it\ngets empty.\n\nChange-Id: Ib7666e235e9b9644144a7c7933afb5e407e506ca\nSigned-off-by: Soumya Koduri <skoduri@redhat.com>\nBUG: 1295107\nSigned-off-by: Soumya Koduri <skoduri@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pfactum/glusterfs/commits/47081c6690a8699e9efee45f6e7e609c5219f830"},{"sha":"3f18d5d3141124c90763dc368ed9fce0fe6e2e57","author":{"email":"39f15b5c9bcef5af1fee3013c5b9b9905213699e@redhat.com","name":"Kaleb S KEITHLEY"},"message":"fuse: use-after-free fix in fuse-bridge, revisited\n\nPrompted by the email exchange in gluster-devel between Oleksandr\nNatalenko, xavi, and soumyak, I looked at this because the fuse client\non the longevity cluster has also been suffering from a serious memory\nleak for some time. (longevity cluster is currently running 3.7.6)\n\nThe longevity cluster manifests the same kernel notifier loop terminated\nlog message the Oleksandr sees, and some sample runs suggest that the\nlength passed to the (sys_)write call is unexpectedly and abnormally large.\n\nBasically this fix\n a) uses correct types for len and rv,\n b) copies the len from potentially incorrectly aligned memory (in a\n    way that should minimize potential performance issues related to\n    accessing unaligned memory.)\n c) changes log level of the kernel notifier loop terminated message\n d) fixes a potential mutex lock/unlock issue\n\nSee\n    Change-Id: Icedb3525706f59803878bb37ef6b4ffe4a986880\n    BUG: 1288857\n    http://review.gluster.org/13274\n\nChange-Id: I1a2f957a95978468baa33c2b1f3667934d88939c\nBUG: 1288922\nSigned-off-by: Kaleb S KEITHLEY <kkeithle@redhat.com>\nReviewed-on: http://review.gluster.org/13275\nSmoke: Gluster Build System <jenkins@build.gluster.com>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nCentOS-regression: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Raghavendra G <rgowdapp@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pfactum/glusterfs/commits/3f18d5d3141124c90763dc368ed9fce0fe6e2e57"},{"sha":"6d4da3d1b37790daa9822e91b77a127d9f1b9add","author":{"email":"ca019b8b0be1f5b5438ff00722db4c4ccf7beb28@redhat.com","name":"Vijay Bellur"},"message":"cluster/dht: Cleanup dict in dht_do_rename()\n\nChange-Id: Ib4b3a843e78eccf5b8e0e7776cd0128013a59a3e\nBUG: 1303945\nSigned-off-by: Vijay Bellur <vbellur@redhat.com>\nReviewed-on: http://review.gluster.org/13322\nCentOS-regression: Gluster Build System <jenkins@build.gluster.com>\nSmoke: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nReviewed-by: Raghavendra G <rgowdapp@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pfactum/glusterfs/commits/6d4da3d1b37790daa9822e91b77a127d9f1b9add"},{"sha":"68168cabae7c2182e419f563a4d56c57b4531609","author":{"email":"5fed6b1878bba2b6032895495b62ed122c85372d@datalab.es","name":"Xavier Hernandez"},"message":"fuse: fix inode and dentry leaks\n\nWhen a readdirp was executed, the nlookup count for each inode of the\nreturned entries was incremented. However the kernel does not increment\nthe counter for '.' and '..' entries.\n\nThis caused that kernel sent forgets with a counter smaller than the\ninode's current value. This prevented these inodes to be retired when\nref count was 0.\n\nChange-Id: I36f3736c86d1cc20adabbbc133ce4edeff62db78\nSigned-off-by: Xavier Hernandez <xhernandez@datalab.es>\nReviewed-on: http://review.gluster.org/13324\nSmoke: Gluster Build System <jenkins@build.gluster.com>\nReviewed-by: Raghavendra Bhat <raghavendra@redhat.com>\nTested-by: Kaleb KEITHLEY <kkeithle@redhat.com>\nCentOS-regression: Gluster Build System <jenkins@build.gluster.com>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nReviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>","distinct":true,"url":"https://api.github.com/repos/pfactum/glusterfs/commits/68168cabae7c2182e419f563a4d56c57b4531609"}]}