summaryrefslogtreecommitdiffstats
path: root/xlators/mgmt/glusterd/src/glusterd-locks.c
diff options
context:
space:
mode:
authorSanju Rakonde <srakonde@redhat.com>2018-09-19 19:49:51 +0530
committerAtin Mukherjee <amukherj@redhat.com>2018-09-20 03:37:44 +0000
commit6a49bce014ac546582cf2409fd9933115406c808 (patch)
tree817c7c37d09afbdcf67d82d9c273a8c28164014f /xlators/mgmt/glusterd/src/glusterd-locks.c
parentb4eedcb4e432d2c2a5411e6cba1dedafba8e3c50 (diff)
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 <srakonde@redhat.com>
Diffstat (limited to 'xlators/mgmt/glusterd/src/glusterd-locks.c')
-rw-r--r--xlators/mgmt/glusterd/src/glusterd-locks.c2
1 files changed, 1 insertions, 1 deletions
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);