From: zhangqilong <zhangqilong3@huawei.com>
To: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: "hare@suse.de" <hare@suse.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: 答复: [PATCH v2] nvme: fix memleak in nvme_ctrl_dhchap_secret_store()
Date: Thu, 1 Dec 2022 01:57:21 +0000 [thread overview]
Message-ID: <83d0a39dc2504639a640bb8ee4875e48@huawei.com> (raw)
In-Reply-To: <20221130133701.GA4267@lst.de>
> On Wed, Nov 30, 2022 at 10:37:45AM +0200, Sagi Grimberg wrote:
> > This is fixed in 6.2 with some of my patches.
>
> And this version conflicts with that.
>
> Zhang, can you please resend a fully tested version against the
> nvme-6.2 branch? Thanks!
It is my pleasure to do that.
I will send a tested version to nvme-6.2 branch!
Thanks,
Zhang
prev parent reply other threads:[~2022-12-01 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 4:49 [PATCH v2] nvme: fix memleak in nvme_ctrl_dhchap_secret_store() Zhang Qilong
2022-11-22 9:44 ` Sagi Grimberg
2022-11-29 4:29 ` Chaitanya Kulkarni
2022-11-29 8:47 ` Christoph Hellwig
2022-11-29 13:40 ` Christoph Hellwig
2022-11-30 3:49 ` 答复: " zhangqilong
2022-11-30 8:37 ` Sagi Grimberg
2022-11-30 13:37 ` Christoph Hellwig
2022-12-01 1:57 ` zhangqilong [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=83d0a39dc2504639a640bb8ee4875e48@huawei.com \
--to=zhangqilong3@huawei.com \
--cc=axboe@fb.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@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