From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Feng Liu <Feng.Liu3@windriver.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6.y] nvme-rdma: unquiesce admin_q before destroy it
Date: Sun, 13 Apr 2025 12:47:38 -0400 [thread overview]
Message-ID: <20250412094432-8b369cf58422246a@stable.kernel.org> (raw)
In-Reply-To: <20250411030455.1085781-1-Feng.Liu3@windriver.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 5858b687559809f05393af745cbadf06dee61295
WARNING: Author mismatch between patch and upstream commit:
Backport author: Feng Liu<Feng.Liu3@windriver.com>
Commit author: Chunguang.xu<chunguang.xu@shopee.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 05b436f3cf65)
Note: The patch differs from the upstream commit:
---
1: 5858b68755980 ! 1: 4d596a05770c2 nvme-rdma: unquiesce admin_q before destroy it
@@ Metadata
## Commit message ##
nvme-rdma: unquiesce admin_q before destroy it
+ [ Upstream commit 5858b687559809f05393af745cbadf06dee61295 ]
+
Kernel will hang on destroy admin_q while we create ctrl failed, such
as following calltrace:
@@ Commit message
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Keith Busch <kbusch@kernel.org>
+ [Minor context change fixed]
+ Signed-off-by: Feng Liu <Feng.Liu3@windriver.com>
+ Signed-off-by: He Zhe <Zhe.He@windriver.com>
## drivers/nvme/host/rdma.c ##
@@ drivers/nvme/host/rdma.c: static int nvme_rdma_setup_ctrl(struct nvme_rdma_ctrl *ctrl, bool new)
+ nvme_rdma_free_io_queues(ctrl);
}
destroy_admin:
- nvme_stop_keep_alive(&ctrl->ctrl);
- nvme_quiesce_admin_queue(&ctrl->ctrl);
- blk_sync_queue(ctrl->ctrl.admin_q);
- nvme_rdma_stop_queue(&ctrl->queues[0]);
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
prev parent reply other threads:[~2025-04-13 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 3:04 [PATCH 6.6.y] nvme-rdma: unquiesce admin_q before destroy it Feng Liu
2025-04-13 16:47 ` Sasha Levin [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=20250412094432-8b369cf58422246a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=Feng.Liu3@windriver.com \
--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;
as well as URLs for NNTP newsgroup(s).