From 6a49bce014ac546582cf2409fd9933115406c808 Mon Sep 17 00:00:00 2001 From: Sanju Rakonde Date: Wed, 19 Sep 2018 19:49:51 +0530 Subject: glusterd: fix crash When huge number of volumes are created, glusterd crash is seen. With the core dump, got to know that mgmt_lock_timer became NULL. Adding a null check for the same, need to explore about the root cause. updates: bz#1630922 Change-Id: I0770063fcbbbf4b24bef29e94b857b20bdfb5b85 Signed-off-by: Sanju Rakonde --- xlators/mgmt/glusterd/src/glusterd-locks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'xlators/mgmt/glusterd/src/glusterd-locks.c') diff --git a/xlators/mgmt/glusterd/src/glusterd-locks.c b/xlators/mgmt/glusterd/src/glusterd-locks.c index 4f2bbf766a7..84e9ca18261 100644 --- a/xlators/mgmt/glusterd/src/glusterd-locks.c +++ b/xlators/mgmt/glusterd/src/glusterd-locks.c @@ -837,7 +837,7 @@ glusterd_mgmt_v3_unlock(const char *name, uuid_t uuid, char *type) name); /* Release owner reference which was held during lock */ - if (mgmt_lock_timer->timer) { + if (mgmt_lock_timer && mgmt_lock_timer->timer) { ret = -1; mgmt_lock_timer_xl = mgmt_lock_timer->xl; GF_VALIDATE_OR_GOTO(this->name, mgmt_lock_timer_xl, out); -- cgit