From: Keith Busch <kbusch@kernel.org>
To: <axboe@kernel.dk>, <hch@lst.de>, <sagi@grimberg.me>,
<linux-nvme@lists.infradead.org>, <shao.mingyin@zte.com.cn>
Cc: <justin.tee@broadcom.com>, <nareshgottumukkala83@gmail.com>,
<paul.ely@broadcom.com>, <kch@nvidia.com>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2 0/6] nvme: fix transport request and queue error handling
Date: Mon, 16 Nov 2026 08:18:29 -0800 [thread overview]
Message-ID: <179484590968.648177.5424785032446332753.b4-ty@kernel.org> (raw)
In-Reply-To: <20261114020245882Mvd6t10TkCZuRWpYFR3m5@zte.com.cn>
On Sat, 14 Nov 2026 02:02:45 +0800 (CST), shao.mingyin@zte.com.cn wrote:
> The six patches fix independent error paths in the NVMe transports.
>
> Patch 1 releases the target request in nvme-loop when SG setup fails.
> nvmet_req_init() has already taken the queue, namespace and reservation
> references, and blk-mq retries the same request, so each failure leaked a
> set of references.
>
> [...]
Thanks, applied to nvme-7.4.
[1/6] nvme-loop: release the target request when SG setup fails
commit: f2937481c28033e10e8a29b8742a767e73c696df
[2/6] nvmet-tcp: only wait for in-capsule data for inline SGLs
commit: 9dac3b1aa2a99e126a5504b7f5bc781c8b2771e0
[3/6] nvme-tcp: require the R2T offset to match the data sent
commit: 347d50d92e25d4b9c50c5f5c1d8b727b9c88d12c
[4/6] nvmet-fcloop: free the LS request when delivery fails
commit: 8c1f99419b6cc51892e259497c8e10a5d079621a
[5/6] nvmet-fc: reject duplicate queue IDs on Create Connection
commit: 153eac284ebf68be74993643e9b2fe2f9b2b1d88
[6/6] nvmet: roll back queue bindings on connection failure
commit: 3f82752e089283eb8204b9d2ebd8246077031173
--
Keith Busch <kbusch@kernel.org>
prev parent reply other threads:[~2026-11-16 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 18:02 shao.mingyin
2026-11-13 18:02 ` [PATCH v2 1/6] nvme-loop: release the target request when SG setup fails shao.mingyin
2026-11-13 18:02 ` [PATCH v2 2/6] nvmet-tcp: only wait for in-capsule data for inline SGLs shao.mingyin
2026-11-13 18:02 ` [PATCH v2 3/6] nvme-tcp: require the R2T offset to match the data sent shao.mingyin
2026-11-13 18:02 ` [PATCH v2 4/6] nvmet-fcloop: free the LS request when delivery fails shao.mingyin
2026-11-13 18:02 ` [PATCH v2 5/6] nvmet-fc: reject duplicate queue IDs on Create Connection shao.mingyin
2026-11-13 18:02 ` [PATCH v2 6/6] nvmet: roll back queue bindings on connection failure shao.mingyin
2026-11-16 16:18 ` 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=179484590968.648177.5424785032446332753.b4-ty@kernel.org \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=justin.tee@broadcom.com \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nareshgottumukkala83@gmail.com \
--cc=paul.ely@broadcom.com \
--cc=sagi@grimberg.me \
--cc=shao.mingyin@zte.com.cn \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®