Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3403206pxf; Mon, 22 Mar 2021 05:46:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyTylohseiMtbi8QWdvWjBQc/ymmvE9fO8GGE5awdt/cdazkQ5y6azKPWk5qHLX6L056mmQ X-Received: by 2002:a17:906:71d3:: with SMTP id i19mr19475338ejk.347.1616417210408; Mon, 22 Mar 2021 05:46:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616417210; cv=none; d=google.com; s=arc-20160816; b=U7zt/1jMgfSB+/Nygm1WTnAXBN388oESPwzLXZbLZW02xVJVM9XED6P09cHkBX6B8M 1L4q2S8OM12eN4FfqdnxD8y2pvr1ae2EXMngZFkjerqiVjMBe/k8sYa8kDMfAbSPnNwC +H18i39jpewI7tapQUXGk0oV+foakdt5UUgV7t53yV8OZxlZqWKPmW6Jg90jWHLkWCdd mL8lPf/++1sWj7teIAvIlc8FNsZ3FkKcWeveBKHf6zokTHxQGE1aTRD0lK3Ztncx1/oW reLMBPtdyua51sszVRnwndRLTUnbeqwNrz95CFvJ77tFvevn2qp+fz+krWEtLImGXF73 s0yA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=I3JuPwVKRJTwZ8iYdsko0NVbae4A39cxrihQAIrEtm8=; b=uRE66NdcKSTB5kOtQNVn0R1Ddux6VCg+9itLM0koYl0GBGQGy3TQVFr1BwwWt64LKC T83fl+tiC4m+sscWWlW8p0/ySwjquxi93gni8XOiOM1oDXdmvu/VF39vAGQ2Oe3p5bjS ojuoGYAOmgcLi0HCfvLaZIlX4/4dI4WoCrsI5Yb8afmMLU/B1pQmim1O2uW/rQrCDVQz rAiu7lsJQEbBvSnmRiXHIeGfUxV1mo16ozfIj5GgnvPKr19br0xT2MdoypNKpatNcT9S 6m21xSRsNH/nmmtJBq07WIPJJUbNFuyzHLx0cIQXnuzVUMg+wCnxSruW82bo7/UsD0gs O2AA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=hyG9Df7W; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y13si10964986edv.220.2021.03.22.05.46.26; Mon, 22 Mar 2021 05:46:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=hyG9Df7W; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230264AbhCVMpS (ORCPT + 99 others); Mon, 22 Mar 2021 08:45:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:56134 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231286AbhCVMiJ (ORCPT ); Mon, 22 Mar 2021 08:38:09 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 68E1B61994; Mon, 22 Mar 2021 12:37:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1616416639; bh=1/IVbCB4L41rAqqxmzsDd9nryLAFzd61mULM2vAsHGI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=hyG9Df7WZ6rJhrec6ekkqAM1b8QALXokZwgDZkcYcu1T4WwmLKwB2o01LrFk0t6T9 9TiiZzm34VLX9X3uVGyLhEDhynSKiWQZigiAyf+4hQbCRoHtajxuBTI0STfTCK543i dPic/R46D/NMBUD/fq6MhAaAn4DQ/tdLhsCwlLuw= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Chao Leng , Sagi Grimberg , Christoph Hellwig , Sasha Levin Subject: [PATCH 5.10 062/157] nvme-rdma: fix possible hang when failing to set io queues Date: Mon, 22 Mar 2021 13:26:59 +0100 Message-Id: <20210322121935.730037892@linuxfoundation.org> X-Mailer: git-send-email 2.31.0 In-Reply-To: <20210322121933.746237845@linuxfoundation.org> References: <20210322121933.746237845@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Sagi Grimberg [ Upstream commit c4c6df5fc84659690d4391d1fba155cd94185295 ] We only setup io queues for nvme controllers, and it makes absolutely no sense to allow a controller (re)connect without any I/O queues. If we happen to fail setting the queue count for any reason, we should not allow this to be a successful reconnect as I/O has no chance in going through. Instead just fail and schedule another reconnect. Reported-by: Chao Leng Fixes: 711023071960 ("nvme-rdma: add a NVMe over Fabrics RDMA host driver") Signed-off-by: Sagi Grimberg Reviewed-by: Chao Leng Signed-off-by: Christoph Hellwig Signed-off-by: Sasha Levin --- drivers/nvme/host/rdma.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/nvme/host/rdma.c b/drivers/nvme/host/rdma.c index 195703013272..8b326508a480 100644 --- a/drivers/nvme/host/rdma.c +++ b/drivers/nvme/host/rdma.c @@ -736,8 +736,11 @@ static int nvme_rdma_alloc_io_queues(struct nvme_rdma_ctrl *ctrl) return ret; ctrl->ctrl.queue_count = nr_io_queues + 1; - if (ctrl->ctrl.queue_count < 2) - return 0; + if (ctrl->ctrl.queue_count < 2) { + dev_err(ctrl->ctrl.device, + "unable to set any I/O queues\n"); + return -ENOMEM; + } dev_info(ctrl->ctrl.device, "creating %d I/O queues.\n", nr_io_queues); -- 2.30.1