[Bugs] [Bug 1228535] New: Memory leak in marker xlator
bugzilla at redhat.com
bugzilla at redhat.com
Fri Jun 5 06:59:52 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1228535
Bug ID: 1228535
Summary: Memory leak in marker xlator
Product: GlusterFS
Version: 3.7.0
Component: quota
Assignee: bugs at gluster.org
Reporter: vbellur at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Depends On: 1227904
+++ This bug was initially created as a clone of Bug #1227904 +++
Description of problem:
Memory leak is observed in marker.
How reproducible: Running iozone in a loop from a fuse client mounting a 3
brick distributed volume seems to trigger the problem.
--- Additional comment from Anand Avati on 2015-06-03 14:28:18 EDT ---
REVIEW: http://review.gluster.org/11074 (features/marker: Cleanup loc in case
of errors) posted (#1) for review on master by Vijay Bellur
(vbellur at redhat.com)
--- Additional comment from Anand Avati on 2015-06-05 01:37:52 EDT ---
COMMIT: http://review.gluster.org/11074 committed in master by Raghavendra G
(rgowdapp at redhat.com)
------
commit d2d7afefd861943f26b290d214fb5213d24b6a02
Author: Vijay Bellur <vbellur at redhat.com>
Date: Wed Jun 3 23:43:55 2015 +0530
features/marker: Cleanup loc in case of errors
Missing loc_wipe() for error paths in mq_readdir_cbk() can
cause memory leaks. loc_wipe() is now done for both happy
and unhappy paths.
Change-Id: I882aa5dcca06e25b56a828767fb2b91a1efaf83b
BUG: 1227904
Signed-off-by: Vijay Bellur <vbellur at redhat.com>
Reviewed-on: http://review.gluster.org/11074
Reviewed-by: Sachin Pandit <spandit at redhat.com>
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Vijaikumar Mallikarjuna <vmallika at redhat.com>
Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
Tested-by: Raghavendra G <rgowdapp at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1227904
[Bug 1227904] Memory leak in marker xlator
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list