summaryrefslogtreecommitdiffstats
path: root/booster
diff options
context:
space:
mode:
authorRaghavendra G <raghavendra@zresearch.com>2009-06-10 07:02:27 +0000
committerAnand V. Avati <avati@dev.gluster.com>2009-06-11 07:29:02 -0700
commit3b99c6d82f9259db54f2d2d0a2520f88e7b12843 (patch)
tree39f49f0f143adfc9cdd83e67a3418747fcfa0c7f /booster
parent943a38e9f8beaaaa7fe741398c573fc458037723 (diff)
booster: fix memory corruption in booster_cleanup
- calling glusterfs_umount_all leads to memory corruption. hence commenting out for timebeing. Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
Diffstat (limited to 'booster')
-rw-r--r--booster/src/booster.c14
1 files changed, 10 insertions, 4 deletions
diff --git a/booster/src/booster.c b/booster/src/booster.c
index 04a8906..4961cc2 100644
--- a/booster/src/booster.c
+++ b/booster/src/booster.c
@@ -1099,10 +1099,16 @@ booster_cleanup (void)
free (booster_glfs_fdtable);
booster_glfs_fdtable = NULL;
- /* FIXME: there may be issues during execution of fini of individual
- xlators due to inconsistent lock states.
- */
- glusterfs_umount_all ();
+ /*
+ * FIXME: there may be issues during execution of fini of individual
+ * xlators due to inconsistent lock states.
+ */
+
+ /*
+ * as above FIXME says, glusterfs_umount_all indeed leads to memory
+ * corruption, hence commenting out
+ */
+ /* glusterfs_umount_all (); */
glusterfs_reset ();
}