From 3b99c6d82f9259db54f2d2d0a2520f88e7b12843 Mon Sep 17 00:00:00 2001 From: Raghavendra G Date: Wed, 10 Jun 2009 07:02:27 +0000 Subject: 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 --- booster/src/booster.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'booster') diff --git a/booster/src/booster.c b/booster/src/booster.c index 04a8906c..4961cc2a 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 (); } -- cgit