From 226d7c442509172b2209515841ef499ec12fc9f2 Mon Sep 17 00:00:00 2001 From: Jeff Darcy Date: Wed, 8 Feb 2017 19:45:46 -0500 Subject: libglusterfs: fix serious leak of xlator_t structures There's a lot of logic (and some long comments) around how to free these structures safely, but then we didn't do it. Now we do. Backport of: > Change-Id: I9731ae75c60e99cc43d33d0813a86912db97fd96 > BUG: 1420571 > Reviewed-on: https://review.gluster.org/16570 Change-Id: I54415b614b277224196f5723bce5a4c5a404d881 BUG: 1420810 Signed-off-by: Jeff Darcy Reviewed-on: https://review.gluster.org/16583 Smoke: Gluster Build System NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System Reviewed-by: Shyamsundar Ranganathan --- libglusterfs/src/xlator.c | 1 + 1 file changed, 1 insertion(+) (limited to 'libglusterfs/src') diff --git a/libglusterfs/src/xlator.c b/libglusterfs/src/xlator.c index 4702ea3eb77..0d09b3fbc82 100644 --- a/libglusterfs/src/xlator.c +++ b/libglusterfs/src/xlator.c @@ -752,6 +752,7 @@ xlator_tree_free_memacct (xlator_t *tree) while (prev) { trav = prev->next; xlator_memrec_free (prev); + GF_FREE (prev); prev = trav; } -- cgit