From: "brookxu.cn" <brookxu.cn@gmail.com>
To: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: hare@suse.de, lengchao@huawei.com
Subject: [PATCH v3 0/4] nvme: various bugs fix & code cleanup
Date: Tue, 3 Dec 2024 11:34:39 +0800 [thread overview]
Message-ID: <cover.1733196360.git.chunguang.xu@shopee.com> (raw)
From: "Chunguang.xu" <chunguang.xu@shopee.com>
Here try to fix the hang issue of nvme-rdma, memory leak issue of
nvme-tcp, and cleanup the relative code of nvme-tcp.
Chunguang.xu (4):
nvme-tcp: fix the memleak while create new ctrl failed
nvme-rdma: unquiesce admin_q before destroy it
nvme-tcp: no need to quiesce admin_q in nvme_tcp_teardown_io_queues()
nvme-tcp: simplify nvme_tcp_teardown_io_queues()
drivers/nvme/host/rdma.c | 8 +-------
drivers/nvme/host/tcp.c | 17 +++++------------
2 files changed, 6 insertions(+), 19 deletions(-)
--
2.25.1
next reply other threads:[~2024-12-03 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 3:34 brookxu.cn [this message]
2024-12-03 3:34 ` [PATCH v3 1/4] nvme-tcp: fix the memleak while create new ctrl failed brookxu.cn
2024-12-03 7:19 ` Hannes Reinecke
2024-12-03 3:34 ` [PATCH v3 2/4] nvme-rdma: unquiesce admin_q before destroy it brookxu.cn
2024-12-03 3:34 ` [PATCH v3 3/4] nvme-tcp: no need to quiesce admin_q in nvme_tcp_teardown_io_queues() brookxu.cn
2024-12-03 3:34 ` [PATCH v3 4/4] nvme-tcp: simplify nvme_tcp_teardown_io_queues() brookxu.cn
2024-12-04 18:20 ` [PATCH v3 0/4] nvme: various bugs fix & code cleanup Keith Busch
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=cover.1733196360.git.chunguang.xu@shopee.com \
--to=brookxu.cn@gmail.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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