Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-nvme@lists.infradead.org,
	Christoph Hellwig <hch@infradead.org>,
	Sagi Grimberg <sagi@grimberg.me>,
	Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH 0/2] nvmet-rdma: fix response resource leak on queue teardown
Date: Mon, 6 Jul 2026 12:57:05 -0600	[thread overview]
Message-ID: <akv6gcd6-mT7lyw9@kbusch-mbp> (raw)
In-Reply-To: <20260629051529.810925-1-shinichiro.kawasaki@wdc.com>

On Mon, Jun 29, 2026 at 02:15:26PM +0900, Shin'ichiro Kawasaki wrote:
> When an nvme target with rdma transport is removed while I/Os are in
> flight, a response can be posted but its send completion is never
> delivered before the connection is torn down. This leaks the request
> SGLs and the RDMA read/write context. The leaks are recreated by
> running blktests nvme/061 with rdma transport and the siw driver [1].
> 
> [1] https://lore.kernel.org/linux-nvme/ajtk1CaN1pBreS4O@shinmob/
> 
> This series addresses the problem. The first patch is a preparation
> refactoring. The second patch fixes the problem by reclaiming memory
> objects on queue QP teardown.

Thanks, applied to nvme-7.3.


      parent reply	other threads:[~2026-07-06 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29  5:15 [PATCH 0/2] nvmet-rdma: fix response resource leak on queue teardown Shin'ichiro Kawasaki
2026-06-29  5:15 ` [PATCH 1/2] nvmet-rdma: factor out response resource cleanup Shin'ichiro Kawasaki
2026-06-30 11:54   ` Christoph Hellwig
2026-06-29  5:15 ` [PATCH 2/2] nvmet-rdma: fix response resource leak on queue teardown Shin'ichiro Kawasaki
2026-06-30 11:54   ` Christoph Hellwig
2026-07-06 18:57 ` Keith Busch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=akv6gcd6-mT7lyw9@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=hch@infradead.org \
    --cc=kch@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=shinichiro.kawasaki@wdc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox