From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2DC1127713; Tue, 9 Jul 2024 11:27:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720524465; cv=none; b=WLnfYJHcf3JMKrh6uPtgL1Gez2Q8Wn6epdM1DjPl+AqRFUvAy4/ULb6Kt+GD7v/FQhlfKnfoyewhmynos6pFKDXb65vtUelbUKHEkeOdPkaX9SAngSypKmjEsTqWfO9RxlGgHYD+yYezb8Fgc3LXXgKf+NFa/JPk/TVh+i+ENSo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720524465; c=relaxed/simple; bh=1guzRbirP0YfTdD3mWl16A+UZmCBerCw7h9/Eh3xmgg=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=lzTMeHaAZ6InTlgSeZVQfYfYYYe90WYAwK0DvAqgg4XXi1m9IyYEu22It1ix8qTanB4ejZMdUb6NLEo+oOEwNMnvzcz4TQhePYiXQuk9042EyC1hzrfPgk1WTwyJqiiLzkfbIeBR7GRRSwxMI/DIsBW0vZWrhODRVc38QbgY/Mk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=pH4n7ILx; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="pH4n7ILx" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AC1D5C3277B; Tue, 9 Jul 2024 11:27:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1720524465; bh=1guzRbirP0YfTdD3mWl16A+UZmCBerCw7h9/Eh3xmgg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=pH4n7ILxzntx3n7sEdgvEBKYiAUe3x52BssD8QmTLPKDyYrBCOwIpZkS8+7cM7tDN TZbC5Pg/oHJUxdVWZd1MEcoBpm291v8nCoZJkLPC51NepxGGvv3jCATHdLhQ11/3p/ 4CQpmXcuow8LlOI27zD5D12iHZ+t6aj1k0nujt/Q= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Alex Turin , Sagi Grimberg , Christoph Hellwig , Keith Busch , Sasha Levin Subject: [PATCH 6.9 189/197] nvmet: fix a possible leak when destroy a ctrl during qp establishment Date: Tue, 9 Jul 2024 13:10:43 +0200 Message-ID: <20240709110716.255187933@linuxfoundation.org> X-Mailer: git-send-email 2.45.2 In-Reply-To: <20240709110708.903245467@linuxfoundation.org> References: <20240709110708.903245467@linuxfoundation.org> User-Agent: quilt/0.67 X-stable: review X-Patchwork-Hint: ignore Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 6.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Sagi Grimberg [ Upstream commit c758b77d4a0a0ed3a1292b3fd7a2aeccd1a169a4 ] In nvmet_sq_destroy we capture sq->ctrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl->sqs and sq->ctrl (for nvme-loop primarily), and drop the final reference on the ctrl. However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But *before* kill_and_confirm of sq->ref (i.e. the admin connect managed to get an sq live reference). In this case, sq->ctrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl. Solve this by re-capturing the sq->ctrl after all inflight request has completed, where for sure sq->ctrl reference is final, and move forward based on that. This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window. Reported-by: Alex Turin Signed-off-by: Sagi Grimberg Reviewed-by: Christoph Hellwig Signed-off-by: Keith Busch Signed-off-by: Sasha Levin --- drivers/nvme/target/core.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c index 2fde22323622e..06f0c587f3437 100644 --- a/drivers/nvme/target/core.c +++ b/drivers/nvme/target/core.c @@ -818,6 +818,15 @@ void nvmet_sq_destroy(struct nvmet_sq *sq) percpu_ref_exit(&sq->ref); nvmet_auth_sq_free(sq); + /* + * we must reference the ctrl again after waiting for inflight IO + * to complete. Because admin connect may have sneaked in after we + * store sq->ctrl locally, but before we killed the percpu_ref. the + * admin connect allocates and assigns sq->ctrl, which now needs a + * final ref put, as this ctrl is going away. + */ + ctrl = sq->ctrl; + if (ctrl) { /* * The teardown flow may take some time, and the host may not -- 2.43.0