From 2f9e555f79ce69668950693ed2e09cfafd2b7ec1 Mon Sep 17 00:00:00 2001 From: Ravishankar N Date: Fri, 29 Jun 2018 11:30:37 +0530 Subject: glusterfsd: Do not process GLUSTERD_BRICK_XLATOR_OP if graph is not ready Problem: If glustershd gets restarted by glusterd due to node reboot/volume start force/ or any thing that changes shd graph (add/remove brick), and index heal is launched via CLI, there can be a chance that shd receives this IPC before the graph is fully active. Thus when it accesses glusterfsd_ctx->active, it crashes. Fix: Since glusterd does not really wait for the daemons it spawned to be fully initialized and can send the request as soon as rpc initialization has succeeded, we just handle it at shd. If glusterfs_graph_activate() is not yet done in shd but glusterd sends GD_OP_HEAL_VOLUME to shd, we fail the request. Change-Id: If6cc07bc5455c4ba03458a36c28b63664496b17d fixes: bz#1596513 Signed-off-by: Ravishankar N --- glusterfsd/src/glusterfsd-mgmt.c | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'glusterfsd/src/glusterfsd-mgmt.c') diff --git a/glusterfsd/src/glusterfsd-mgmt.c b/glusterfsd/src/glusterfsd-mgmt.c index 863765d644f..7122fc0d127 100644 --- a/glusterfsd/src/glusterfsd-mgmt.c +++ b/glusterfsd/src/glusterfsd-mgmt.c @@ -681,6 +681,13 @@ glusterfs_handle_translator_op (rpcsvc_request_t *req) ctx = glusterfsd_ctx; active = ctx->active; + if (!active) { + ret = -1; + gf_msg (this->name, GF_LOG_ERROR, EAGAIN, glusterfsd_msg_38, + "Not processing brick-op no. %d since volume graph is " + "not yet active.", xlator_req.op); + goto out; + } any = active->first; input = dict_new (); ret = dict_unserialize (xlator_req.input.input_val, -- cgit