From: Shivam Kumar <kumar.shivam43666@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: Greg KH <greg@kroah.com>,
security@kernel.org, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
Keith Busch <kbusch@kernel.org>,
stable@vger.kernel.org,
Shivam Kumar <kumar.shivam43666@gmail.com>
Subject: [PATCH] nvmet-tcp: fix a hang on queue teardown with data digest
Date: Mon, 31 Aug 2026 21:47:18 -0400 [thread overview]
Message-ID: <20260901014718.2835558-1-kumar.shivam43666@gmail.com> (raw)
With data digest on, a command that has received all its data waits for
the digest in NVMET_TCP_RECV_DDGST. has_data_in() is already false there,
so need_data_in() is too, and nvmet_tcp_uninit_data_in_cmds() skips it on
teardown even though it still holds the nvmet_req_init() reference. The SQ
percpu_ref never drains, nvmet_sq_destroy() blocks forever in
wait_for_completion(), and the nvmet-wq release worker is stuck.
An unauthenticated host on an allow_any_host subsystem hits this by
negotiating data digest, sending a write's data but not the trailing
digest, and closing the connection. Each leaked command wedges a release
worker; a few stall queue teardown entirely, and with hung_task_panic the
box goes down.
Drop the reference for a command left in RECV_DDGST from
nvmet_tcp_release_queue_work(), before rcv_state is cleared. A command
that failed nvmet_req_init() never took one, so skip it.
Fixes: 872d26a391da ("nvmet-tcp: add NVMe over TCP target driver")
Cc: stable@vger.kernel.org
Signed-off-by: Shivam Kumar <kumar.shivam43666@gmail.com>
Assisted-by: Claude
---
drivers/nvme/target/tcp.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
--- a/drivers/nvme/target/tcp.c
+++ b/drivers/nvme/target/tcp.c
@@ -1640,6 +1640,19 @@
nvmet_tcp_restore_socket_callbacks(queue);
cancel_delayed_work_sync(&queue->tls_handshake_tmo_work);
cancel_work_sync(&queue->io_work);
+
+ /*
+ * A command that has received all of its data and is only waiting
+ * for the data digest sits in RECV_DDGST: need_data_in() is already
+ * false, so nvmet_tcp_uninit_data_in_cmds() below skips it, yet it
+ * still holds the reference from nvmet_req_init(). Drop it here,
+ * while rcv_state still reflects it, so the SQ percpu_ref can drain
+ * and nvmet_sq_destroy() can complete. INIT_FAILED took no ref.
+ */
+ if (queue->rcv_state == NVMET_TCP_RECV_DDGST && queue->cmd &&
+ !(queue->cmd->flags & NVMET_TCP_F_INIT_FAILED))
+ nvmet_req_uninit(&queue->cmd->req);
+
/* stop accepting incoming data */
queue->rcv_state = NVMET_TCP_RECV_ERR;
--
2.34.1
next reply other threads:[~2026-09-01 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 1:47 Shivam Kumar [this message]
2026-09-07 23:11 ` [PATCH] nvmet-tcp: fix a hang on queue teardown with data digest Shivam Kumar
2026-09-10 22:32 ` Keith Busch
2026-09-11 21:15 ` Sagi Grimberg
2026-09-12 5:39 ` [PATCH v2] " Shivam Kumar
2026-09-21 17:06 ` Shivam Kumar
2026-09-28 15:30 ` Shivam Kumar
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=20260901014718.2835558-1-kumar.shivam43666@gmail.com \
--to=kumar.shivam43666@gmail.com \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=security@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.