From: Hannes Reinecke <hare@suse.de>
To: "brookxu.cn" <brookxu.cn@gmail.com>,
kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: lengchao@huawei.com
Subject: Re: [PATCH v3 1/4] nvme-tcp: fix the memleak while create new ctrl failed
Date: Tue, 3 Dec 2024 08:19:21 +0100 [thread overview]
Message-ID: <d1b103bb-fc9b-45dc-b637-75ce9fdb320c@suse.de> (raw)
In-Reply-To: <b4957fa602ebb3af58872042d8e3bf1adf3b386b.1733196360.git.chunguang.xu@shopee.com>
On 12/3/24 04:34, brookxu.cn wrote:
> From: "Chunguang.xu" <chunguang.xu@shopee.com>
>
> Now while we create new ctrl failed, we have not free the
> tagset occupied by admin_q, here try to fix it.
>
> Fixes: fd1418de10b9 ("nvme-tcp: avoid open-coding nvme_tcp_teardown_admin_queue()")
> Signed-off-by: Chunguang.xu <chunguang.xu@shopee.com>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/nvme/host/tcp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> index 3e416af2659f..55abfe5e1d25 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -2278,7 +2278,7 @@ static int nvme_tcp_setup_ctrl(struct nvme_ctrl *ctrl, bool new)
> }
> destroy_admin:
> nvme_stop_keep_alive(ctrl);
> - nvme_tcp_teardown_admin_queue(ctrl, false);
> + nvme_tcp_teardown_admin_queue(ctrl, new);
> return ret;
> }
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2024-12-03 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 3:34 [PATCH v3 0/4] nvme: various bugs fix & code cleanup brookxu.cn
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 [this message]
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=d1b103bb-fc9b-45dc-b637-75ce9fdb320c@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=brookxu.cn@gmail.com \
--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