From 7c3cc485054e4ede1efb358552135b432fb7047a Mon Sep 17 00:00:00 2001 From: Mohit Agrawal Date: Sat, 10 Feb 2018 12:25:15 +0530 Subject: glusterfsd: Memleak in glusterfsd process while brick mux is on Problem: At the time of stopping the volume while brick multiplex is enabled memory is not cleanup from all server side xlators. Solution: To cleanup memory for all server side xlators call fini in glusterfs_handle_terminate after send GF_EVENT_CLEANUP notification to top xlator. BUG: 1544090 Signed-off-by: Mohit Agrawal Note: Run all test-cases in separate build (https://review.gluster.org/19574) with same patch after enable brick mux forcefully, all test cases are passed. Change-Id: Ia10dc7f2605aa50f2b90b3fe4eb380ba9299e2fc --- xlators/protocol/server/src/server.c | 1 - 1 file changed, 1 deletion(-) (limited to 'xlators/protocol/server/src/server.c') diff --git a/xlators/protocol/server/src/server.c b/xlators/protocol/server/src/server.c index 30546e87b8d..758264a638b 100644 --- a/xlators/protocol/server/src/server.c +++ b/xlators/protocol/server/src/server.c @@ -1507,7 +1507,6 @@ server_notify (xlator_t *this, int32_t event, void *data, ...) victim->name); /* we need the protocol/server xlator here as 'this' */ glusterfs_autoscale_threads (ctx, -1, this); - default_notify (victim, GF_EVENT_CLEANUP, data); } break; -- cgit