From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18])
	(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 831083AEF4A
	for <linux-kernel@vger.kernel.org>; Wed, 19 Aug 2026 15:33:43 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1787153624; cv=none; b=WIA6gsMRRWEFd+Pqw0eAdumFReSjJ+tNZGeJQc7zc3jpNpcGHHVHdo0vQzSUV176l3bPS+pzqrUc/JWnzUPOtAwr0+oAqwfaPF/+4IbszTwcHl2cdC1189HD90L8iIyQjSZB+SmnzIPbm8vDpTxVMSTsG6RqpiUBc22i78nhHlI=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1787153624; c=relaxed/simple;
	bh=Z+obtHm7hXT2S6sFzgSpj2nG/aYMzx8Fys0Tl+mZ748=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=rDuLXmc0BC1muMBzX1C2oHEfQHHVF51g6LTjS5vyH+SsbjyE8biM9TV4U95yOsElIz/rwI66FnrohOucb+jcOzz78QoNa2hLevSD4rMiLjmvLSLGvI65AnorFwmxzt6yBakYzIIgf7ykPhG1DVGxkDVRjo75yUM/tpuvhEHLMso=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=EVFcE+w+; arc=none smtp.client-ip=100.103.45.18
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="EVFcE+w+"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 018311F000E9;
	Wed, 19 Aug 2026 15:33:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org;
	s=k20260515; t=1787153623;
	bh=Z+obtHm7hXT2S6sFzgSpj2nG/aYMzx8Fys0Tl+mZ748=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To;
	b=EVFcE+w+O6j6/iZZ5X4XUExFXLr3WzFK07KrUCHYgWlOl9cz5/w4Adm9f9lVwvSob
	 U4JukQOiHztjfMdAkmv9PXPiLaGDaIs4J0yQQrILoUSAoodFtAz33fTp2Sb2aOJwF8
	 y0dravcyKqq6x73s8Gq/mSnW1I+bejM+CRfCE6jxHrs8sAy3kmhS62Swlmo2uv+5Js
	 fxE7vQuqPRWHQ5bTfqXMYFqYWb2xxlj3RrdCqhzw08MKGyhzi6JV8etvwJjCw2fI0a
	 bB6p7qSV6ac/N4XevKVTprrOpG9hVkptGtEXVhlqLh1Z2Ttx/y6MLVVsETAay3zfK8
	 zt6c08Wmv7LKA==
Date: Wed, 19 Aug 2026 09:33:41 -0600
From: Keith Busch <kbusch@kernel.org>
To: Xixin Liu <liuxixin@kylinos.cn>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
	kch@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmet-rdma: fix queue leak when connect backlog is
 exceeded
Message-ID: <aoXM1U0IP1of5l8q@kbusch-mbp>
References: <nvmet-rdma-backlog-leak.v1.git.liuxixin@kylinos.cn>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <nvmet-rdma-backlog-leak.v1.git.liuxixin@kylinos.cn>

On Thu, Aug 13, 2026 at 02:42:01PM +0800, Xixin Liu wrote:
> When pending disconnecting queues exceed the backlog limit, the
> connect path only drops the device reference and leaks the newly
> allocated queue and its IB resources.

Thanks, applied to nvme-7.3.